Skip to content

typo #14273

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 31, 2018
Merged

typo #14273

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
typo
  • Loading branch information
@DarrylvanderPeijl
DarrylvanderPeijl authored Aug 30, 2018
commit fc292e508d74f2408ecd868929e34d8560f53be7
2 changes: 1 addition & 1 deletion .../windows/sql/virtual-machines-windows-portal-sql-availability-group-overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ The diagram illustrates the parts of a complete SQL Server Availability Group in

The key difference for an Availability Group in Azure Virtual Machines is that the Azure virtual machines, require a [load balancer](../../../load-balancer/load-balancer-overview.md). The load balancer holds the IP addresses for the availability group listener. If you have more than one availability group each group requires a listener. One load balancer can support multiple listeners.

When you are ready to build a SQL Server availability aroup on Azure Virtual Machines, refer to these tutorials.
When you are ready to build a SQL Server availability group on Azure Virtual Machines, refer to these tutorials.

## Automatically create an availability group from a template

Expand Down