status

alexbuckgit · alexbuckgit · commit f55b5064e9e2 · 2024-05-24T01:43:33.000-04:00
diff --git a/articles/azure-resource-manager/custom-providers/create-custom-provider-quickstart-powershell.md b/articles/azure-resource-manager/custom-providers/create-custom-provider-quickstart-powershell.md
@@ -22,16 +22,12 @@ In this quickstart, you learn how to create your own Azure custom resource provi
 
 ## Requirements
 
-If you don't have an Azure subscription, create a [free](https://azure.microsoft.com/free/) account
-before you begin.
+If you don't have an Azure subscription, create a [free](https://azure.microsoft.com/free/) account before you begin.
 
-If you choose to use PowerShell locally, this article requires that you install the Az PowerShell
-module and connect to your Azure account using the
-[Connect-AzAccount](/powershell/module/az.accounts/connect-azaccount) cmdlet. For more information
-about installing the Az PowerShell module, see
+If you choose to use PowerShell locally, this article requires that you install the Az PowerShell module and connect to your Azure account using the
+[Connect-AzAccount](/powershell/module/az.accounts/connect-azaccount) cmdlet. For more information about installing the Az PowerShell module, see
 [Install Azure PowerShell](/powershell/azure/install-azure-powershell). If you choose to use Cloud Shell, see
-[Overview of Azure Cloud Shell](../../cloud-shell/overview.md) for
-more information.
+[Overview of Azure Cloud Shell](../../cloud-shell/overview.md) for more information.
 
 > [!IMPORTANT]
 > While the **Az.CustomProviders** PowerShell module is in preview, you must install it separately using
@@ -42,8 +38,7 @@ more information.
 Install-Module -Name Az.CustomProviders
 ```
 
-If you have multiple Azure subscriptions, choose the appropriate subscription in which the resources
-should be billed. Select a specific subscription using the
+If you have multiple Azure subscriptions, choose the appropriate subscription in which the resources should be billed. Select a specific subscription using the
 [Set-AzContext](/powershell/module/az.accounts/set-azcontext) cmdlet.
 
 ```azurepowershell-interactive
@@ -52,10 +47,8 @@ Set-AzContext -SubscriptionId 00000000-0000-0000-0000-000000000000
 
 ## Create a resource group
 
-Create an [Azure resource group](../../azure-resource-manager/management/overview.md)
-using the [New-AzResourceGroup](/powershell/module/az.resources/new-azresourcegroup)
-cmdlet. A resource group is a logical container in which Azure resources are deployed and managed as
-a group.
+Create an [Azure resource group](../../azure-resource-manager/management/overview.md) using the [New-AzResourceGroup](/powershell/module/az.resources/new-azresourcegroup)
+cmdlet. A resource group is a logical container in which Azure resources are deployed and managed as a group.
 
 The following example creates a resource group with the specified name and in the specified location.
 
@@ -66,8 +59,7 @@ New-AzResourceGroup -Name myResourceGroup -Location westus2
 ## Create a custom resource provider
 
 To create or update a custom resource provider, you use the
-[New-AzCustomProvider](/powershell/module/az.customproviders/new-azcustomprovider) cmdlet as shown
-in the following example.
+[New-AzCustomProvider](/powershell/module/az.customproviders/new-azcustomprovider) cmdlet as shown in the following example.
 
 ```azurepowershell-interactive
 New-AzCustomProvider -ResourceGroupName myResourceGroup -Name Namespace.Type -Location westus2 -ResourceType @{Name='CustomRoute1'; Endpoint='https://www.contoso.com/'}
@@ -76,8 +68,7 @@ New-AzCustomProvider -ResourceGroupName myResourceGroup -Name Namespace.Type -Lo
 ## Get the custom resource provider manifest
 
 To retrieve information about the custom resource provider manifest, you use the
-[Get-AzCustomProvider](/powershell/module/az.customproviders/get-azcustomprovider) cmdlet as shown
-in the following example.
+[Get-AzCustomProvider](/powershell/module/az.customproviders/get-azcustomprovider) cmdlet as shown in the following example.
 
 ```azurepowershell-interactive
 Get-AzCustomProvider -ResourceGroupName myResourceGroup -Name Namespace.Type | Format-List
@@ -106,8 +97,7 @@ Get-AzCustomProviderAssociation -Scope $resourceId -Name MyAssoc
 
 ## Clean up resources
 
-If the resources created in this article aren't needed, you can delete them by running the following
-examples.
+If the resources created in this article aren't needed, you can delete them by running the following examples.
 
 ### Delete an association
 
diff --git a/articles/azure-resource-manager/management/resource-graph-samples.md b/articles/azure-resource-manager/management/resource-graph-samples.md
@@ -8,10 +8,8 @@ ms.custom: subject-resourcegraph-sample, devx-track-azurepowershell, devx-track-
 
 # Azure Resource Graph sample queries for Azure Resource Manager
 
-This page is a collection of [Azure Resource Graph](../../governance/resource-graph/overview.md)
-sample queries for Azure Resource Manager. For a complete list of Azure Resource Graph samples, see
-[Resource Graph samples by Category](../../governance/resource-graph/samples/samples-by-category.md)
-and [Resource Graph samples by Table](../../governance/resource-graph/samples/samples-by-table.md).
+This page is a collection of [Azure Resource Graph](../../governance/resource-graph/overview.md) sample queries for Azure Resource Manager. For a complete list of Azure Resource Graph samples, see
+[Resource Graph samples by Category](../../governance/resource-graph/samples/samples-by-category.md) and [Resource Graph samples by Table](../../governance/resource-graph/samples/samples-by-table.md).
 
 ## Sample queries for tags
 
diff --git a/articles/batch/batch-virtual-network.md b/articles/batch/batch-virtual-network.md
@@ -11,8 +11,7 @@ When you create an Azure Batch pool, you can provision the pool in a subnet of a
 
 ## Why use a Virtual Network?
 
-Compute nodes in a pool can communicate with each other, such as to run multi-instance tasks, without requiring a
-separate Virtual Network. However, by default, nodes in a pool can't communicate with any virtual machine (VM) that is outside of the pool, such as license or file servers.
+Compute nodes in a pool can communicate with each other, such as to run multi-instance tasks, without requiring a separate Virtual Network. However, by default, nodes in a pool can't communicate with any virtual machine (VM) that is outside of the pool, such as license or file servers.
 
 To allow compute nodes to communicate securely with other virtual machines, or with an on-premises network, you can provision the pool in a subnet of a Virtual Network.
 
@@ -33,8 +32,7 @@ To allow compute nodes to communicate securely with other virtual machines, or w
 
 * The subnet specified for the pool must have enough unassigned IP addresses to accommodate the number of VMs targeted for the pool, enough to accommodate the `targetDedicatedNodes` and `targetLowPriorityNodes` properties of the pool. If the subnet doesn't have enough unassigned IP addresses, the pool partially allocates the compute nodes, and a resize error occurs.
 
-* If you aren't using [Simplified Compute Node Communication](simplified-compute-node-communication.md), you need to resolve your Azure Storage endpoints by using any custom DNS servers that serve your virtual network. Specifically,
-URLs of the form `<account>.table.core.windows.net`, `<account>.queue.core.windows.net`, and
+* If you aren't using [Simplified Compute Node Communication](simplified-compute-node-communication.md), you need to resolve your Azure Storage endpoints by using any custom DNS servers that serve your virtual network. Specifically, URLs of the form `<account>.table.core.windows.net`, `<account>.queue.core.windows.net`, and
 `<account>.blob.core.windows.net` should be resolvable.
 
 * Multiple pools can be created in the same virtual network or in the same subnet (as long as it has sufficient address space). A single pool can't exist across multiple virtual networks or subnets.
@@ -49,10 +47,7 @@ pools are [deprecated](https://azure.microsoft.com/updates/azure-batch-cloudserv
 > [Simplified](simplified-compute-node-communication.md) node communication mode
 > is where the compute nodes initiate communication to the Batch Service.
 
-* Any virtual network or peered virtual network that will be used for Batch pools should not have overlapping IP address ranges with software defined networking
-or routing on compute nodes. A common source for conflicts is from the use of a [container runtime](batch-docker-container-workloads.md), such as docker. Docker
-will create a default network bridge with a defined subnet range of `172.17.0.0/16`. Any services running within a virtual network in that default IP address
-space will conflict with services on the compute node, such as remote access via SSH.
+* Any virtual network or peered virtual network that will be used for Batch pools should not have overlapping IP address ranges with software defined networking or routing on compute nodes. A common source for conflicts is from the use of a [container runtime](batch-docker-container-workloads.md), such as docker. Docker will create a default network bridge with a defined subnet range of `172.17.0.0/16`. Any services running within a virtual network in that default IP address space will conflict with services on the compute node, such as remote access via SSH.
 
 ## Pools in Virtual Machine Configuration
 
@@ -74,15 +69,11 @@ Requirements:
 
 ### Network security groups for Virtual Machine Configuration pools: Batch default
 
-Batch creates a network security group (NSG) at the network interface level of each Virtual Machine Scale
-Set deployment within a Batch pool. For pools that don't have public IP addresses under `simplified` compute
-node communication, NSGs aren't created.
+Batch creates a network security group (NSG) at the network interface level of each Virtual Machine Scale Set deployment within a Batch pool. For pools that don't have public IP addresses under `simplified` compute node communication, NSGs aren't created.
 
-In order to provide the necessary communication between compute nodes and the Batch service, these NSGs are
-configured such that:
+In order to provide the necessary communication between compute nodes and the Batch service, these NSGs are configured such that:
 
-* Inbound TCP traffic on ports 29876 and 29877 from Batch service IP addresses that correspond to the
-BatchNodeManagement.*region* service tag. This rule is only created in `classic` pool communication mode.
+* Inbound TCP traffic on ports 29876 and 29877 from Batch service IP addresses that correspond to the BatchNodeManagement.*region* service tag. This rule is only created in `classic` pool communication mode.
 * Inbound TCP traffic on port 22 (Linux nodes) or port 3389 (Windows nodes) to permit remote access for SSH or RDP on default ports, respectively. For certain types of multi-instance tasks on Linux, such as MPI, you may need to allow SSH traffic for IPs in the subnet containing Batch compute nodes. Certain MPI runtimes may require launching over SSH, which is typically routed on private IP address space. This traffic might be blocked per subnet-level NSG rules.
 * Outbound any traffic on port 443 to Batch service IP addresses that correspond to the BatchNodeManagement.*region* service tag.
 * Outbound traffic on any port to the virtual network. This rule might be amended per subnet-level NSG rules.
@@ -93,8 +84,7 @@ BatchNodeManagement.*region* service tag. This rule is only created in `classic`
 
 ### Network security groups for Virtual Machine Configuration pools: Specifying subnet-level rules
 
-If you have an NSG associated with the subnet for Batch compute nodes, you must configure this
-NSG with at least the inbound and outbound security rules that are shown in the following tables.
+If you have an NSG associated with the subnet for Batch compute nodes, you must configure this NSG with at least the inbound and outbound security rules that are shown in the following tables.
 
 > [!WARNING]
 > Batch service IP addresses can change over time. Therefore, you should use the
@@ -108,12 +98,7 @@ NSG with at least the inbound and outbound security rules that are shown in the
 | BatchNodeManagement.*region* [service tag](../../articles/virtual-network/network-security-groups-overview.md#service-tags) | 29876-29877 | TCP | Classic | Yes |
 | Source IP addresses for remotely accessing compute nodes | 3389 (Windows), 22 (Linux) | TCP | Classic or Simplified | No |
 
-Configure inbound traffic on port 3389 (Windows) or 22 (Linux) only if you need to permit remote access
-to the compute nodes from outside sources on default RDP or SSH ports, respectively. You might need to allow
-SSH traffic on Linux if you require support for multi-instance tasks with certain Message Passing Interface
-(MPI) runtimes in the subnet containing the Batch compute nodes as traffic may be blocked per subnet-level NSG
-rules. MPI traffic is typically over private IP address space, but can vary between MPI runtimes and runtime
-configuration. Allowing traffic on these ports isn't strictly required for the pool compute nodes to be usable.
+Configure inbound traffic on port 3389 (Windows) or 22 (Linux) only if you need to permit remote access to the compute nodes from outside sources on default RDP or SSH ports, respectively. You might need to allow SSH traffic on Linux if you require support for multi-instance tasks with certain Message Passing Interface (MPI) runtimes in the subnet containing the Batch compute nodes as traffic may be blocked per subnet-level NSG rules. MPI traffic is typically over private IP address space, but can vary between MPI runtimes and runtime configuration. Allowing traffic on these ports isn't strictly required for the pool compute nodes to be usable.
 You can also disable default remote access on these ports through configuring [pool endpoints](pool-endpoint-configuration.md).
 
 #### Outbound security rules
@@ -123,14 +108,7 @@ You can also disable default remote access on these ports through configuring [p
 | BatchNodeManagement.*region* [service tag](../../articles/virtual-network/network-security-groups-overview.md#service-tags) | 443 | * | Simplified | Yes |
 | Storage.*region* [service tag](../../articles/virtual-network/network-security-groups-overview.md#service-tags) | 443 | TCP | Classic | Yes |
 
-Outbound to BatchNodeManagement.*region* service tag is required in `classic` pool communication mode
-if you're using Job Manager tasks or if your tasks must communicate back to the Batch service. For outbound to
-BatchNodeManagement.*region* in `simplified` pool communication mode, the Batch service currently only
-uses TCP protocol, but UDP might be required for future compatibility. For
-[pools without public IP addresses](simplified-node-communication-pool-no-public-ip.md)
-using `simplified` communication mode and with a node management private endpoint, an NSG isn't needed.
-For more information about outbound security rules for the BatchNodeManagement.*region* service tag, see
-[Use simplified compute node communication](simplified-compute-node-communication.md).
+Outbound to BatchNodeManagement.*region* service tag is required in `classic` pool communication mode if you're using Job Manager tasks or if your tasks must communicate back to the Batch service. For outbound to BatchNodeManagement.*region* in `simplified` pool communication mode, the Batch service currently only uses TCP protocol, but UDP might be required for future compatibility. For [pools without public IP addresses](simplified-node-communication-pool-no-public-ip.md) using `simplified` communication mode and with a node management private endpoint, an NSG isn't needed. For more information about outbound security rules for the BatchNodeManagement.*region* service tag, see [Use simplified compute node communication](simplified-compute-node-communication.md).
 
 ## Pools in the Cloud Services Configuration
 
@@ -158,7 +136,7 @@ Configure inbound traffic on port 3389 for Windows if you need to permit RDP acc
 
 | Source IP addresses | Source ports | Destination | Destination ports | Protocol | Action |
 | --- | --- | --- | --- | --- | --- |
-Any <br /><br />Although this rule effectively requires *allow all*, the Batch service applies an ACL rule at the level of each node that filters out all non-Batch service IP addresses. | * | Any | 10100, 20100, 30100 | TCP | Allow |
+| Any <br /><br />Although this rule effectively requires *allow all*, the Batch service applies an ACL rule at the level of each node that filters out all non-Batch service IP addresses. | * | Any | 10100, 20100, 30100 | TCP | Allow |
 | Optional, to allow RDP access to compute nodes. | * | Any | 3389 | TCP | Allow |
 
 **Outbound security rules**
diff --git a/articles/communication-services/resources/troubleshooting/voice-video-calling/audio-issues/overview.md b/articles/communication-services/resources/troubleshooting/voice-video-calling/audio-issues/overview.md
@@ -23,10 +23,7 @@ To establish a voice call with good quality, several factors must be considered.
 
 All of these factors are important from an end-to-end perspective.
 
-Device and network issues are considered external problems from the perspective of the ACS Calling SDK.
-Your application should integrate the [User Facing Diagnostics API](../../../../concepts/voice-video-calling/user-facing-diagnostics.md)
-to monitor device and network issues and display warning messages accordingly.
-In this way, users are aware of the issue and can troubleshoot on their own.
+Device and network issues are considered external problems from the perspective of the ACS Calling SDK. Your application should integrate the [User Facing Diagnostics API](../../../../concepts/voice-video-calling/user-facing-diagnostics.md) to monitor device and network issues and display warning messages accordingly. In this way, users are aware of the issue and can troubleshoot on their own.
 
 ## Common issues in audio calls
 Here we list several common audio issues, along with potential causes for each issue:
diff --git a/articles/container-registry/resource-graph-samples.md b/articles/container-registry/resource-graph-samples.md
@@ -10,10 +10,8 @@ ms.custom: subject-resourcegraph-sample
 ---
 # Azure Resource Graph sample queries for Azure Container Registry
 
-This page is a collection of [Azure Resource Graph](../governance/resource-graph/overview.md) sample
-queries for Azure Container Registry. For a complete list of Azure Resource Graph samples, see
-[Resource Graph samples by Category](../governance/resource-graph/samples/samples-by-category.md)
-and [Resource Graph samples by Table](../governance/resource-graph/samples/samples-by-table.md).
+This page is a collection of [Azure Resource Graph](../governance/resource-graph/overview.md) sample queries for Azure Container Registry. For a complete list of Azure Resource Graph samples, see
+[Resource Graph samples by Category](../governance/resource-graph/samples/samples-by-category.md) and [Resource Graph samples by Table](../governance/resource-graph/samples/samples-by-table.md).
 
 ## Sample queries
 
diff --git a/articles/cosmos-db/mongodb/how-to-configure-multi-region-write.md b/articles/cosmos-db/mongodb/how-to-configure-multi-region-write.md
@@ -36,8 +36,8 @@ MongoDB connection strings supports the “appName” parameter, which is a mean
 The appName parameter can be in one of the following formats​:
 
 ```powershell
-appName=<user-workload-name>​
-appName=<user-workload-name>@<preferred-write-region>​
+appName=<user-workload-name>
+appName=<user-workload-name>@<preferred-write-region>
 appName=<user-workload-name>@<cosmosdb-account-name>@<preferred-write-region>
 ```
 
diff --git a/articles/cosmos-db/nosql/kafka-connector-sink.md b/articles/cosmos-db/nosql/kafka-connector-sink.md
@@ -260,9 +260,8 @@ If you have non-JSON data on your source topic in Kafka and attempt to read it u
 
 ```console
 org.apache.kafka.connect.errors.DataException: Converting byte[] to Kafka Connect data failed due to serialization error:
-…
-org.apache.kafka.common.errors.SerializationException: java.io.CharConversionException: Invalid UTF-32 character 0x1cfa7e2 (above 0x0010ffff) at char #1, byte #7)
-
+...
+org.apache.kafka.common.errors.SerializationException: java.io.CharConversionException: Invalid UTF-32 character 0x1cfa7e2 (above 0x0010ffff) at char #1, byte #7
 ```
 
 This error is likely caused by data in the source topic being serialized in either Avro or another format such as CSV string.
@@ -313,10 +312,9 @@ This scenario is applicable when you try to use the Avro converter to read data
 ```console
 org.apache.kafka.connect.errors.DataException: my-topic-name
 at io.confluent.connect.avro.AvroConverter.toConnectData(AvroConverter.java:97)
-…
+...
 org.apache.kafka.common.errors.SerializationException: Error deserializing Avro message for id -1
 org.apache.kafka.common.errors.SerializationException: Unknown magic byte!
-
 ```
 
 **Solution**: Check the source topic’s serialization format. Then, either switch Kafka Connect’s sink connector to use the right converter or switch the upstream format to Avro.
diff --git a/articles/cosmos-db/postgresql/concepts-cluster.md b/articles/cosmos-db/postgresql/concepts-cluster.md
diff --git a/articles/cosmos-db/postgresql/concepts-connection-pool.md b/articles/cosmos-db/postgresql/concepts-connection-pool.md
