Merge pull request #180776 from MicrosoftDocs/master

11/22 PM Publish

Author: huypub

.vscode/settings.json

@@ -414,7 +414,7 @@ Follow these steps to create your App Service resources and publish your project
 :::zone target="docs" pivot="development-environment-cli"
 <!-- markdownlint-enable MD044 -->
 
-1. Sign into your Azure account by using the [`az login`](/cli/reference-index#az_login) command and following the prompt:
+1. Sign into your Azure account by using the [`az login`](/cli/azure/reference-index#az_login) command and following the prompt:
 
     ```azurecli
     az login

articles/active-directory/governance/media/create-access-review/upon-completion-settings-additional-receivers.png

@@ -426,7 +426,7 @@ message associated with error code {errorCode}
 
 **Cause:** This error occurs when Application Gateway can't verify the validity of the certificate.
 
-**Solution:** To resolve this issue, verify that the certificate on your server was created properly. For example, you can use [OpenSSL](https://www.openssl.org/docs/man1.0.2/man1/verify.html) to verify the certificate and its properties and then try reuploading the certificate to the Application Gateway HTTP settings.
+**Solution:** To resolve this issue, verify that the certificate on your server was created properly. For example, you can use [OpenSSL](https://www.openssl.org/docs/manmaster/man1/verify.html) to verify the certificate and its properties and then try reuploading the certificate to the Application Gateway HTTP settings.
 
 ## Backend health status: unknown
 

articles/app-service/quickstart-dotnetcore.md

@@ -422,7 +422,7 @@ Before you run the command, make these changes:
 #### Request
 
 ```bash
-curl -v -i POST "https://{endpoint}/formrecognizer/documentModels/prebuilt-invoice:analyze?api-version=2021-09-30-preview" -H "Content-Type: application/json" -H "Ocp-Apim-Subscription-Key: {subscription key}" --data-ascii "{'urlsource': '{your-document-url}'}"
+curl -v -i POST "https://{endpoint}/formrecognizer/documentModels/prebuilt-invoice:analyze?api-version=2021-09-30-preview" -H "Content-Type: application/json" -H "Ocp-Apim-Subscription-Key: {subscription key}" --data-ascii "{'urlSource': '{your-document-url}'}"
 ```
 
 #### Operation-Location

articles/application-gateway/application-gateway-backend-health-troubleshooting.md

@@ -4,7 +4,7 @@ description: Learn what services are supported by availability zones and underst
 author: prsandhu
 ms.service: azure
 ms.topic: conceptual
-ms.date: 10/01/2021
+ms.date: 11/22/2021
 ms.author: rarco
 ms.reviewer: cynthn
 ms.custom: references_regions
@@ -122,6 +122,8 @@ In the Product Catalog, always-available services are listed as "non-regional" s
 | [Azure Firewall](../firewall/deploy-availability-zone-powershell.md)  | ![An icon that signifies this service is zone redundant.](media/icon-zone-redundant.svg)  |
 | [Azure Firewall Manager](../firewall-manager/quick-firewall-policy.md)  | ![An icon that signifies this service is zone redundant.](media/icon-zone-redundant.svg)  |
 | [Azure Functions](https://azure.github.io/AppService/2021/08/25/App-service-support-for-availability-zones.html)  | ![An icon that signifies this service is zone redundant.](media/icon-zone-redundant.svg)  |
+| [Azure IoT Hub](../iot-hub/iot-hub-ha-dr.md#availability-zones) | ![An icon that signifies this service is zone redundant.](media/icon-zone-redundant.svg)  |
+| [Azure IoT Hub Device Provisioning Service](../iot-dps/about-iot-dps.md#availability) | ![An icon that signifies this service is zone redundant.](media/icon-zone-redundant.svg)  |
 | [Azure Kubernetes Service (AKS)](../aks/availability-zones.md)  | ![An icon that signifies this service is zone redundant.](media/icon-zone-redundant.svg) ![An icon that signifies this service is zonal](media/icon-zonal.svg)  |
 | [Azure Monitor](../azure-monitor/logs/availability-zones.md)  | ![An icon that signifies this service is zone redundant.](media/icon-zone-redundant.svg)  |
 | [Azure Monitor: Application Insights](../azure-monitor/logs/availability-zones.md)  | ![An icon that signifies this service is zone redundant.](media/icon-zone-redundant.svg)  |

articles/applied-ai-services/form-recognizer/quickstarts/try-v3-rest-api.md

@@ -34,7 +34,7 @@ Some Azure-attached services are only available when they can be directly reache
 ||**Indirectly connected**|**Directly connected**|**Never connected**|
 |---|---|---|---|
 |**Description**|Indirectly connected mode offers most of the management services locally in your environment with no direct connection to Azure.  A minimal amount of data must be sent to Azure for inventory and billing purposes _only_. It is exported to a file and uploaded to Azure at least once per month.  No direct or continuous connection to Azure is required.  Some features and services which require a connection to Azure will not be available.|Directly connected mode offers all of the available services when a direct connection can be established with Azure. Connections are always initiated _from_ your environment to Azure and use standard ports and protocols such as HTTPS/443.|No data can be sent to or from Azure in any way.|
-|**Current availability**| Available |Available in preview.|Not currently supported.|
+|**Current availability**| Available |Available|Not currently supported.|
 |**Typical use cases**|On-premises data centers that don’t allow connectivity in or out of the data region of the data center due to business or regulatory compliance policies or out of concerns of external attacks or data exfiltration.  Typical examples: Financial institutions, health care, government. <br/><br/>Edge site locations where the edge site doesn’t typically have connectivity to the Internet.  Typical examples: oil/gas or military field applications.  <br/><br/>Edge site locations that have intermittent connectivity with long periods of outages.  Typical examples: stadiums, cruise ships. | Organizations who are using public clouds.  Typical examples: Azure, AWS or Google Cloud.<br/><br/>Edge site locations where Internet connectivity is typically present and allowed.  Typical examples: retail stores, manufacturing.<br/><br/>Corporate data centers with more permissive policies for connectivity to/from their data region of the datacenter to the Internet.  Typical examples: Non-regulated businesses, small/medium sized businesses|Truly "air-gapped" environments where no data under any circumstances can come or go from the data environment. Typical examples: top secret government facilities.|
 |**How data is sent to Azure**|There are three options for how the billing and inventory data can be sent to Azure:<br><br> 1) Data is exported out of the data region by an automated process that has connectivity to both the secure data region and Azure.<br><br>2) Data is exported out of the data region by an automated process within the data region, automatically copied to a less secure region, and an automated process in the less secure region uploads the data to Azure.<br><br>3) Data is manually exported by a user within the secure region, manually brought out of the secure region, and manually uploaded to Azure. <br><br>The first two options are an automated continuous process that can be scheduled to run frequently so there is minimal delay in the transfer of data to Azure subject only to the available connectivity to Azure.|Data is automatically and continuously sent to Azure.|Data is never sent to Azure.|
 
@@ -50,7 +50,7 @@ Some Azure-attached services are only available when they can be directly reache
 |**Automatic upgrades and patching**|Supported<br/>The data controller must either have direct access to the Microsoft Container Registry (MCR) or the container images need to be pulled from MCR and pushed to a local, private container registry that the data controller has access to.|Supported<br/>**Pending availability in directly connected.**|
 |**Automatic backup and restore**|Supported<br/>Automatic local backup and restore.|Supported<br/>In addition to automated local backup and restore, you can _optionally_ send backups to Azure Backup for long-term, off-site retention. **Pending availability in directly connected mode.**|
 |**Monitoring**|Supported<br/>Local monitoring using Grafana and Kibana dashboards.|Supported<br/>In addition to local monitoring dashboards, you can _optionally_ send monitoring data and logs to Azure Monitor for at-scale monitoring of multiple sites in one place. |
-|**Authentication**|Use local username/password for data controller and dashboard authentication. Use SQL and Postgres logins or Active Directory (AD is not currently supported, will be in preview soon) for connectivity to database instances.  Use K8s authentication providers for authentication to the Kubernetes API.|In addition to or instead of the authentication methods for the indirectly connected mode, you can _optionally_ use Azure Active Directory. **Pending availability in directly connected mode**|
+|**Authentication**|Use local username/password for data controller and dashboard authentication. Use SQL and Postgres logins or Active Directory (AD is not currently supported) for connectivity to database instances.  Use K8s authentication providers for authentication to the Kubernetes API.|In addition to or instead of the authentication methods for the indirectly connected mode, you can _optionally_ use Azure Active Directory. **Pending availability in directly connected mode**|
 |**Role-based access control (RBAC)**|Use Kubernetes RBAC on Kubernetes API. Use SQL and Postgres RBAC for database instances.|You can use Azure Active Directory and Azure RBAC. **Pending availability in directly connected mode**|
 |**Microsoft Defender for Cloud**|Not supported|Planned for future|
 

articles/availability-zones/az-region.md

@@ -47,7 +47,7 @@ Regardless of the option you choose, during the creation process you will need t
 - **Data controller username** - Any username for the data controller administrator user.
 - **Data controller password** - A password for the data controller administrator user.
 - **Name of your Kubernetes namespace** - the name of the Kubernetes namespace that you want to create the data controller in.
-- **Connectivity mode** - Connectivity mode determines the degree of connectivity from your Azure Arc-enabled data services environment to Azure. Indirect connectivity mode is generally available. Direct connectivity mode is in preview.  For information, see [connectivity mode](./connectivity.md). 
+- **Connectivity mode** - Connectivity mode determines the degree of connectivity from your Azure Arc-enabled data services environment to Azure. For information, see [connectivity mode](./connectivity.md). 
 - **Azure subscription ID** - The Azure subscription GUID for where you want the data controller resource in Azure to be created.
 - **Azure resource group name** - The name of the resource group where you want the data controller resource in Azure to be created.
 - **Azure location** - The Azure location where the data controller resource metadata will be stored in Azure. For a list of available regions, see [Azure global infrastructure / Products by region](https://azure.microsoft.com/global-infrastructure/services/?products=azure-arc). The metadata and billing information about the Azure resources managed by the data controller that you are deploying will be stored only in the location in Azure that you specify as the location parameter. If you are deploying in the directly connected mode, the location parameter for the data controller will be the same as the location of the custom location resource that you target.

articles/azure-arc/data/connectivity.md

@@ -71,7 +71,7 @@ When you're creating Azure Arc-enabled data services, regardless of the service
 - **Username**: The username for the Kibana/Grafana administrator user.
 - **Password**: The password for the Kibana/Grafana administrator user.
 - **Name of your Kubernetes namespace**: The name of the Kubernetes namespace where you want to create the data controller.
-- **Connectivity mode**: Determines the degree of connectivity from your Azure Arc-enabled data services environment to Azure. *Indirect* connectivity mode is generally available, and *direct* connectivity mode is in preview. Your choice of connectivity mode determines the options for deployment methods. For more information, see [Connectivity modes and requirements](./connectivity.md).
+- **Connectivity mode**: Determines the degree of connectivity from your Azure Arc-enabled data services environment to Azure. Your choice of connectivity mode determines the options for deployment methods. For more information, see [Connectivity modes and requirements](./connectivity.md).
 - **Azure subscription ID**: The Azure subscription GUID for where you want to create the data controller resource in Azure. All Azure Arc-enabled SQL managed instances and Azure Database for PostgreSQL Hyperscale server groups are also created in and billed to this subscription.
 - **Azure resource group name**: The name of the resource group where you want to create the data controller resource in Azure. All Azure Arc-enabled SQL managed instances and Azure Database for PostgreSQL Hyperscale server groups are also created in this resource group.
 - **Azure location**: The Azure location where the data controller resource metadata will be stored in Azure. For a list of available regions, see the [Products available by region](https://azure.microsoft.com/global-infrastructure/services/?products=azure-arc) page for Azure global infrastructure. The metadata and billing information about the Azure resources that are managed by your deployed data controller is stored only in the location in Azure that you specify as the location parameter. If you're deploying in direct connectivity mode, the location parameter for the data controller is the same as the location of your targeted custom location resource.

articles/azure-arc/data/create-data-controller.md

@@ -18,9 +18,9 @@ ms.date: 10/11/2021
 Azure Cache for Redis 6.0 is now generally available. The new version includes:
 
 - Redis Streams, a new data type
-- performance enhancements
-- enhanced developer productivity
-- boosts security
+- Performance enhancements
+- Enhanced developer productivity
+- Boosts security
 
 You can now use an append-only data structure, Redis Streams, to ingest, manage, and make sense of data that is continuously being generated.