Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into rolyon-aadroles-admin-units-members-powershell

rolyon · rolyon · commit adb702336b6e · 2022-09-22T11:05:57.000-07:00
diff --git a/articles/app-service/configure-language-java.md b/articles/app-service/configure-language-java.md
@@ -440,7 +440,7 @@ By default, any public or private certificates [uploaded to App Service Linux](c
 
 More configuration may be necessary for encrypting your JDBC connection with certificates in the Java Key Store. Refer to the documentation for your chosen JDBC driver.
 
-- [PostgreSQL](https://jdbc.postgresql.org/documentation/head/ssl-client.html)
+- [PostgreSQL](https://jdbc.postgresql.org/documentation/ssl/)
 - [SQL Server](/sql/connect/jdbc/connecting-with-ssl-encryption)
 - [MySQL](https://dev.mysql.com/doc/connector-j/5.1/en/connector-j-reference-using-ssl.html)
 - [MongoDB](https://mongodb.github.io/mongo-java-driver/3.4/driver/tutorials/ssl/)
@@ -610,7 +610,7 @@ These instructions apply to all database connections. You will need to fill plac
 
 | Database   | Driver Class Name                             | JDBC Driver                                                                      |
 |------------|-----------------------------------------------|------------------------------------------------------------------------------------------|
-| PostgreSQL | `org.postgresql.Driver`                        | [Download](https://jdbc.postgresql.org/download.html)                                    |
+| PostgreSQL | `org.postgresql.Driver`                        | [Download](https://jdbc.postgresql.org/download/)                                    |
 | MySQL      | `com.mysql.jdbc.Driver`                        | [Download](https://dev.mysql.com/downloads/connector/j/) (Select "Platform Independent") |
 | SQL Server | `com.microsoft.sqlserver.jdbc.SQLServerDriver` | [Download](/sql/connect/jdbc/download-microsoft-jdbc-driver-for-sql-server#download)                                                           |
 
@@ -920,7 +920,7 @@ These instructions apply to all database connections. You will need to fill plac
 
 | Database   | Driver Class Name                             | JDBC Driver                                                                              |
 |------------|-----------------------------------------------|------------------------------------------------------------------------------------------|
-| PostgreSQL | `org.postgresql.Driver`                        | [Download](https://jdbc.postgresql.org/download.html)                                    |
+| PostgreSQL | `org.postgresql.Driver`                        | [Download](https://jdbc.postgresql.org/download/)                                    |
 | MySQL      | `com.mysql.jdbc.Driver`                        | [Download](https://dev.mysql.com/downloads/connector/j/) (Select "Platform Independent") |
 | SQL Server | `com.microsoft.sqlserver.jdbc.SQLServerDriver` | [Download](/sql/connect/jdbc/download-microsoft-jdbc-driver-for-sql-server#download)     |
 
diff --git a/articles/azure-cache-for-redis/cache-network-isolation.md b/articles/azure-cache-for-redis/cache-network-isolation.md
@@ -18,19 +18,19 @@ Azure Private Link provides private connectivity from a virtual network to Azure
 
 ### Advantages of Private Link
 
-* Supported on Basic, Standard, and Premium Azure Cache for Redis instances.
-* By using [Azure Private Link](../private-link/private-link-overview.md), you can connect to an Azure Cache instance from your virtual network via a private endpoint. The endpoint is assigned a private IP address in a subnet within the virtual network. With this private link, cache instances are available from both within the VNet and publicly.  
-* Once a private endpoint is created, access to the public network can be restricted through the `publicNetworkAccess` flag. This flag is set to `Disabled` by default, which will only allow private link access. You can set the value to `Enabled` or `Disabled` with a PATCH request. For more information, see [Azure Cache for Redis with Azure Private Link](cache-private-link.md).
-* All external cache dependencies won't affect the VNet's NSG rules.
+- Supported on Basic, Standard, and Premium Azure Cache for Redis instances.
+- By using [Azure Private Link](../private-link/private-link-overview.md), you can connect to an Azure Cache instance from your virtual network via a private endpoint. The endpoint is assigned a private IP address in a subnet within the virtual network. With this private link, cache instances are available from both within the VNet and publicly.  
+- Once a private endpoint is created, access to the public network can be restricted through the `publicNetworkAccess` flag. This flag is set to `Disabled` by default, which will only allow private link access. You can set the value to `Enabled` or `Disabled` with a PATCH request. For more information, see [Azure Cache for Redis with Azure Private Link](cache-private-link.md).
+- All external cache dependencies won't affect the VNet's NSG rules.
 
 ### Limitations of Private Link
 
-* Network security groups (NSG) are disabled for private endpoints. However, if there are other resources on the subnet, NSG enforcement will apply to those resources.
-* Currently, portal console support, and persistence to firewall storage accounts aren't supported.
-* To connect to a clustered cache, `publicNetworkAccess` needs to be set to `Disabled` and there can only be one private endpoint connection.
+- Network security groups (NSG) are disabled for private endpoints. However, if there are other resources on the subnet, NSG enforcement will apply to those resources.
+- Currently, portal console support, and persistence to firewall storage accounts aren't supported.
+- To connect to a clustered cache, `publicNetworkAccess` needs to be set to `Disabled`, and there can only be one private endpoint connection.
 
 > [!NOTE]
-> When adding a private endpoint to a cache instance, all Redis traffic will be moved to the private endpoint because of the DNS.
+> When adding a private endpoint to a cache instance, all Redis traffic is moved to the private endpoint because of the DNS.
 > Ensure previous firewall rules are adjusted before.  
 
 ## Azure Virtual Network injection
@@ -39,30 +39,32 @@ VNet is the fundamental building block for your private network in Azure. VNet e
 
 ### Advantages of VNet injection
 
-* When an Azure Cache for Redis instance is configured with a VNet, it's not publicly addressable. It can only be accessed from virtual machines and applications within the VNet.  
-* When VNet is combined with restricted NSG policies, it helps reduce the risk of data exfiltration.
-* VNet deployment provides enhanced security and isolation for your Azure Cache for Redis. Subnets, access control policies, and other features further restrict access.
-* Geo-replication is supported.
+- When an Azure Cache for Redis instance is configured with a VNet, it's not publicly addressable. It can only be accessed from virtual machines and applications within the VNet.  
+- When VNet is combined with restricted NSG policies, it helps reduce the risk of data exfiltration.
+- VNet deployment provides enhanced security and isolation for your Azure Cache for Redis. Subnets, access control policies, and other features further restrict access.
+- Geo-replication is supported.
 
 ### Limitations of VNet injection
 
-* VNet injected caches are only available for Premium Azure Cache for Redis.
-* When using a VNet injected cache, you must change your VNet to cache dependencies such as CRLs/PKI, AKV, Azure Storage, Azure Monitor, and more.  
+- VNet injected caches are only available for Premium Azure Cache for Redis.
+- When using a VNet injected cache, you must change your VNet to cache dependencies such as CRLs/PKI, AKV, Azure Storage, Azure Monitor, and more.  
 
 ## Azure Firewall rules
 
 [Azure Firewall](../firewall/overview.md) is a managed, cloud-based network security service that protects your Azure VNet resources. It’s a fully stateful firewall as a service with built-in high availability and unrestricted cloud scalability. You can centrally create, enforce, and log application and network connectivity policies across subscriptions and virtual networks.  
 
 ### Advantages of firewall rules
 
-* When firewall rules are configured, only client connections from the specified IP address ranges can connect to the cache. Connections from Azure Cache for Redis monitoring systems are always permitted, even if firewall rules are configured. NSG rules that you define are also permitted.  
+- When firewall rules are configured, only client connections from the specified IP address ranges can connect to the cache. Connections from Azure Cache for Redis monitoring systems are always permitted, even if firewall rules are configured. NSG rules that you define are also permitted.  
 
 ### Limitations of firewall rules
 
-* Firewall rules can be used with VNet injected caches, but not private endpoints currently.
+- Firewall rules can be used with VNet injected caches, but not private endpoints.
+- Firewall rules configuration is available for all Basic, Standard, and Premium tiers.
+- Firewall rules configuration isn't available for Enterprise nor Enterprise Flash tiers.
 
 ## Next steps
 
-* Learn how to configure a [VNet injected cache for a Premium Azure Cache for Redis instance](cache-how-to-premium-vnet.md).
-* Learn how to configure [firewall rules for all Azure Cache for Redis tiers](cache-configure.md#firewall).
-* Learn how to [configure private endpoints for all Azure Cache for Redis tiers](cache-private-link.md).
+- Learn how to configure a [VNet injected cache for a Premium Azure Cache for Redis instance](cache-how-to-premium-vnet.md).
+- Learn how to configure [firewall rules for all Azure Cache for Redis tiers](cache-configure.md#firewall).
+- Learn how to [configure private endpoints for all Azure Cache for Redis tiers](cache-private-link.md).
diff --git a/articles/data-factory/connector-azure-databricks-delta-lake.md b/articles/data-factory/connector-azure-databricks-delta-lake.md
@@ -56,7 +56,7 @@ During copy activity execution, if the cluster you configured has been terminate
 
 2. In the **Databricks Runtime Version** drop-down, select a Databricks runtime version.
 
-3. Turn on [Auto Optimize](/azure/databricks/delta/optimizations/auto-optimize) by adding the following properties to your [Spark configuration](/azure/databricks/clusters/configure#spark-config):
+3. Turn on [Auto Optimize](/azure/databricks/optimizations/auto-optimize) by adding the following properties to your [Spark configuration](/azure/databricks/clusters/configure#spark-config):
 
    ```
    spark.databricks.delta.optimizeWrite.enabled true
diff --git a/articles/healthcare-apis/events/events-disable-delete-workspace.md b/articles/healthcare-apis/events/events-disable-delete-workspace.md
@@ -1,37 +1,36 @@
 ---
-title: Disable events and delete workspaces - Azure Health Data Services
-description: This article provides resources on how to disable Events and delete workspaces.
+title: Disable Events and delete workspaces - Azure Health Data Services
+description: This article provides resources on how to disable the Events service and delete workspaces.
 services: healthcare-apis
 author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: how-to
-ms.date: 07/06/2022
+ms.date: 09/22/2022
 ms.author: jasteppe
 ---
 
-# Disable events and delete workspaces
+# Disable Events and delete workspaces
 
 In this article, you'll learn how to disable the Events feature and delete workspaces in the Azure Health Data Services.
 
-## Disable events
+## Disable Events
 
-To disable events from sending event messages for a single Event Subscription, the Event Subscription must be deleted.
+To disable Events from sending event messages for a single **Event Subscription**, the **Event Subscription** must be deleted.
 
-1. Select the Event Subscription to be deleted. In this example, we'll be selecting an Event Subscription named **fhir-events**.
+1. Select the **Event Subscription** to be deleted. In this example, we'll be selecting an Event Subscription named **fhir-events**.
 
    :::image type="content" source="media/disable-delete-workspaces/events-select-subscription.png" alt-text="Screenshot of Events subscriptions and select event subscription to be deleted." lightbox="media/disable-delete-workspaces/events-select-subscription.png":::
 
 2. Select **Delete** and confirm the Event Subscription deletion.
 
    :::image type="content" source="media/disable-delete-workspaces/events-select-subscription-delete.png" alt-text="Screenshot of events subscriptions and select delete and confirm the event subscription to be deleted." lightbox="media/disable-delete-workspaces/events-select-subscription-delete.png":::
 
-3. To completely disable Events, delete all Event Subscriptions so that no Event Subscriptions remain.
+3. To completely disable Events, delete all **Event Subscriptions** so that no **Event Subscriptions** remain.
 
    :::image type="content" source="media/disable-delete-workspaces/events-disable-no-subscriptions.png" alt-text="Screenshot of Events subscriptions and delete all event subscriptions to disable events." lightbox="media/disable-delete-workspaces/events-disable-no-subscriptions.png":::
 
 > [!NOTE]
->
 > The Fast Healthcare Interoperability Resources (FHIR&#174;) service will automatically go into an **Updating** status to disable the Events extension when a full delete of Event Subscriptions is executed. The FHIR service will remain online while the operation is completing.
 
 ## Delete workspaces
@@ -46,7 +45,7 @@ As an example:
 
 ## Next steps
 
-For more information about how to troubleshoot Events, see
+For more information about troubleshooting Events, see the Events troubleshooting guide:
 
 >[!div class="nextstepaction"]
 >[Troubleshoot Events](./events-troubleshooting-guide.md)
diff --git a/articles/mysql/flexible-server/concepts-high-availability.md b/articles/mysql/flexible-server/concepts-high-availability.md
@@ -163,7 +163,7 @@ You can disable HA on a server after you create it. Billing stops immediately.
 You need to be able to mitigate downtime for your application even when you're not using HA. Service downtime, like scheduled patches, minor version upgrades, or customer-initiated operations like scaling of compute can be performed during scheduled maintenance windows. To mitigate application impact for Azure-initiated maintenance tasks, you can schedule them on a day of the week and time that minimizes the impact on the application.</br>
 
 - **Can I use a read replica for an HA-enabled server?**</br>
-Read replicas aren't supported for HA servers. This feature is on our roadmap, and we're working to make it available soon.</br>
+Yes, read replicas are supported for HA servers.</br>
 
 - **Can I use Data-in Replication for HA servers?**</br>
 Data-in Replication isn't supported for HA servers. But Data-in Replication for HA servers is on our roadmap and will be available soon. For now, if you want to use Data-in Replication for migration, you can follow these steps:
diff --git a/articles/mysql/flexible-server/concepts-read-replicas.md b/articles/mysql/flexible-server/concepts-read-replicas.md
@@ -75,6 +75,9 @@ Azure Database for MySQL Flexible Server provides the **Replication lag in secon
 
 If you see increased replication lag, refer to [troubleshooting replication latency](./../howto-troubleshoot-replication-latency.md) to troubleshoot and understand possible causes.
 
+>[!IMPORTANT]
+>Read Replica on HA server uses storage based replication technology, which no longer uses 'SLAVE_IO_RUNNING' metric available in MySQL's 'SHOW SLAVE STATUS' command. The value of it will always be displayed as "No" and is not indicative of replication status.
+
 ## Stop replication
 
 You can stop replication between a source and a replica. After replication is stopped between a source server and a read replica, the replica becomes a standalone server. The data in the standalone server is the data that was available on the replica at the time the stop replication command was started. The standalone server doesn't catch up with the source server.
@@ -138,7 +141,6 @@ If GTID is enabled on a source server (`gtid_mode` = ON), newly created replicas
 
 | Scenario | Limitation/Consideration |
 |:-|:-|
-| Replica on server with HA enabled | Not supported |
 | Replica on server in Burstable Pricing Tier| Not supported |
 | Cross region read replication | Not supported |
 | Pricing | The cost of running the replica server is based on the region where the replica server is running |
diff --git a/articles/mysql/flexible-server/how-to-read-replicas-cli.md b/articles/mysql/flexible-server/how-to-read-replicas-cli.md
@@ -18,8 +18,6 @@ In this article, you will learn how to create and manage read replicas in the Az
 
 [!Note]
 >
-> * Replica is not supported on high availability enabled server.
->
 > * If GTID is enabled on a primary server (`gtid_mode` = ON), newly created replicas will also have GTID enabled and use GTID based replication. To learn more refer to [Global transaction identifier (GTID)](concepts-read-replicas.md#global-transaction-identifier-gtid)
 
 ## Azure CLI
diff --git a/articles/mysql/flexible-server/how-to-read-replicas-portal.md b/articles/mysql/flexible-server/how-to-read-replicas-portal.md
@@ -16,9 +16,7 @@ ms.date: 06/17/2021
 In this article, you will learn how to create and manage read replicas in the Azure Database for MySQL flexible server using the Azure portal.
 
 > [!Note]
->
-> * Replica is not supported on high availability enabled server.
->
+> 
 > * If GTID is enabled on a primary server (`gtid_mode` = ON), newly created replicas will also have GTID enabled and use GTID based replication. To learn more refer to [Global transaction identifier (GTID)](concepts-read-replicas.md#global-transaction-identifier-gtid)
 
 ## Prerequisites
diff --git a/articles/mysql/flexible-server/whats-new.md b/articles/mysql/flexible-server/whats-new.md
@@ -23,6 +23,17 @@ This article summarizes new releases and features in Azure Database for MySQL -
 > This article contains references to the term slave, a term that Microsoft no longer uses. When the term is removed from the software, we'll remove it from this article.
 
 ## September 2022
+- **Read replica for HA enabled Azure Database for MySQL - Flexible Server (General Availability)**
+
+  The read replica feature allows you to replicate data from an Azure Database for MySQL flexible server to a read-only server. You can replicate the source server to up to 10 replicas. This functionality is now extended to support HA enabled servers within same region.[Learn more](concepts-read-replicas.md)
+
+
+
+- **Azure Active Directory authentication for Azure Database for MySQL – Flexible Server (Public Preview)**
+
+  You can now authenticate to Azure Database for MySQL - Flexible server using Microsoft Azure Active Directory (Azure AD) using identities. With Azure AD authentication, you can manage database user identities and other Microsoft services in a central location, which simplifies permission management. [Learn More](concepts-azure-ad-authentication.md)
+
+
 
 - **Customer managed keys data encryption – Azure Database for MySQL – Flexible Server (Preview)**
 
diff --git a/articles/postgresql/single-server/concepts-connection-libraries.md b/articles/postgresql/single-server/concepts-connection-libraries.md
@@ -24,7 +24,7 @@ Most language client libraries used to connect to PostgreSQL server are external
 | Python | [psycopg](https://www.psycopg.org/) | DB API 2.0-compliant | [Download](https://sourceforge.net/projects/adodbapi/) |
 | PHP | [php-pgsql](https://secure.php.net/manual/en/book.pgsql.php) | Database extension | [Install](https://secure.php.net/manual/en/pgsql.installation.php) |
 | Node.js | [Pg npm package](https://www.npmjs.com/package/pg) | Pure JavaScript non-blocking client | [Install](https://www.npmjs.com/package/pg) |
-| Java | [JDBC](https://jdbc.postgresql.org/) | Type 4 JDBC driver | [Download](https://jdbc.postgresql.org/download.html)  |
+| Java | [JDBC](https://jdbc.postgresql.org/) | Type 4 JDBC driver | [Download](https://jdbc.postgresql.org/download/)  |
 | Ruby | [Pg gem](https://deveiate.org/code/pg/) | Ruby Interface | [Download](https://rubygems.org/downloads/pg-0.20.0.gem) |
 | Go | [Package pq](https://godoc.org/github.com/lib/pq) | Pure Go postgres driver | [Install](https://github.com/lib/pq/blob/master/README.md) |
 | C\#/ .NET | [Npgsql](https://www.npgsql.org/) | ADO.NET Data Provider | [Download](https://dotnet.microsoft.com/download) |
diff --git a/articles/virtual-desktop/sandbox.md b/articles/virtual-desktop/sandbox.md
@@ -65,7 +65,7 @@ To publish Windows Sandbox to your host pool using PowerShell:
 1. Connect to Azure using one of the following methods:
   
    - Open a PowerShell prompt on your local device. Run the `Connect-AzAccount` cmdlet to sign in to your Azure account. For more information, see [Sign in with Azure PowerShell](/powershell/azure/authenticate-azureps).
-   - Sign in to [the Azure portal](https://portal.azure.com/) and open [Azure Cloud Shell](https://github.com/MicrosoftDocs/azure-docs-pr/pull/cloud-shell/overview.md) with PowerShell as the shell type.
+   - Sign in to [the Azure portal](https://portal.azure.com/) and open [Azure Cloud Shell](../cloud-shell/overview.md) with PowerShell as the shell type.
 
 2. Run the following cmdlet to get a list of all the Azure tenants your account has access to:
   
diff --git a/articles/virtual-machines/workloads/sap/high-availability-guide-rhel-pacemaker.md b/articles/virtual-machines/workloads/sap/high-availability-guide-rhel-pacemaker.md
diff --git a/articles/virtual-machines/workloads/sap/high-availability-guide-suse-pacemaker.md b/articles/virtual-machines/workloads/sap/high-availability-guide-suse-pacemaker.md
diff --git a/articles/virtual-wan/global-hub-profile.md b/articles/virtual-wan/global-hub-profile.md

Original file line number	Diff line number	Diff line change
`@@ -18,8 +18,6 @@ In this article, you will learn how to create and manage read replicas in the Az`
`18`	`18`
`19`	`19`	`[!Note]`
`20`	`20`	`>`
`21`		`-> * Replica is not supported on high availability enabled server.`
`22`		`->`
`23`	`21`	> * If GTID is enabled on a primary server (`gtid_mode` = ON), newly created replicas will also have GTID enabled and use GTID based replication. To learn more refer to [Global transaction identifier (GTID)](concepts-read-replicas.md#global-transaction-identifier-gtid)
`24`	`22`
`25`	`23`	`## Azure CLI`