You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/virtual-network/virtual-networks-faq.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -209,7 +209,7 @@ If you change your DNS server list, you need to perform a DHCP lease renewal on
209
209
Azure-provided DNS is a multitenant DNS service from Microsoft. Azure registers all of your VMs and cloud service role instances in this service. This service provides name resolution:
210
210
211
211
* By host name for VMs and role instances in the same cloud service.
212
-
* By fully qualified domain main (FQDN) for VMs and role instances in the same virtual network.
212
+
* By fully qualified domain name (FQDN) for VMs and role instances in the same virtual network.
213
213
214
214
To learn more about DNS, see [Name resolution for resources in Azure virtual networks](virtual-networks-name-resolution-for-vms-and-role-instances.md).
215
215
@@ -345,7 +345,7 @@ No. You must set the [FlowTimeoutInMinutes](/powershell/module/az.network/set-az
345
345
346
346
```Powershell
347
347
$Allvnet = Get-AzVirtualNetwork
348
-
$time = 4 #The value should be 4 to 30 minutes (inclusive) to enable tracking, or null to disable tracking.
348
+
$time = 4 #The value should be from 4 to 30 minutes (inclusive) to enable tracking, or null to disable tracking.
349
349
ForEach ($vnet in $Allvnet)
350
350
{
351
351
$vnet.FlowTimeoutInMinutes = $time
@@ -506,7 +506,7 @@ Certain services (such as Azure SQL and Azure Cosmos DB) allow exceptions to the
506
506
Turning on the service endpoints on the network side can lead to a connectivity drop, because the source IP changes from a public IPv4 address to a private address. Setting up virtual network ACLs on the Azure service side before turning on service endpoints on the network side can help avoid a connectivity drop.
507
507
508
508
>[!NOTE]
509
-
> If you enable Service Endpoint on certain services like "Microsoft.AzureActiveDirectory" you can see IPV6 address connections on Sign-In Logs. Microsoft use an internal IPV6 private range for this type of connection.
509
+
> If you enable Service Endpoint on certain services like "Microsoft.AzureActiveDirectory" you can see IPv6 address connections on Sign-In Logs. Microsoft use an internal IPv6 private range for this type of connection.
510
510
511
511
### Do all Azure services reside in the Azure virtual network that the customer provides? How does a virtual network service endpoint work with Azure services?
0 commit comments