Merging changes synced from https://github.com/MicrosoftDocs/azure-docs-pr (branch live)

Author: Banani-Rath

articles/active-directory/external-identities/media/self-service-sign-up-user-flow/enable-self-service-sign-up.png

@@ -5,7 +5,7 @@ services: active-directory
 ms.service: active-directory
 ms.subservice: B2B
 ms.topic: how-to
-ms.date: 04/26/2022
+ms.date: 10/12/2022
 
 ms.author: mimart
 author: msmimart
@@ -61,9 +61,10 @@ Next, you'll create the user flow for self-service sign-up and add it to an appl
 
    ![Add a new user flow button](media/self-service-sign-up-user-flow/new-user-flow.png)
 
-5. On the **Create** page, enter a **Name** for the user flow. Note that the name is automatically prefixed with **B2X_1_**.
-6. In the **Identity providers** list, select one or more identity providers that your external users can use to log into your application. **Azure Active Directory Sign up** is selected by default. (See [Before you begin](#before-you-begin) earlier in this article to learn how to add identity providers.)
-7. Under **User attributes**, choose the attributes you want to collect from the user. For additional attributes, select **Show more**. For example, select **Show more**, and then choose attributes and claims for **Country/Region**, **Display Name**, and **Postal Code**. Select **OK**.
+5. Select the user flow type (for example, **Sign up and sign in**), and then select the version (**Recommended** or **Preview**).
+6. On the **Create** page, enter a **Name** for the user flow. Note that the name is automatically prefixed with **B2X_1_**.
+7. In the **Identity providers** list, select one or more identity providers that your external users can use to log into your application. **Azure Active Directory Sign up** is selected by default. (See [Before you begin](#before-you-begin) earlier in this article to learn how to add identity providers.)
+8. Under **User attributes**, choose the attributes you want to collect from the user. For additional attributes, select **Show more**. For example, select **Show more**, and then choose attributes and claims for **Country/Region**, **Display Name**, and **Postal Code**. Select **OK**.
 
    ![Create a new user flow page](media/self-service-sign-up-user-flow/create-user-flow.png)
 
@@ -86,7 +87,7 @@ You can choose order in which the attributes are displayed on the sign-up page.
 
 ## Add applications to the self-service sign-up user flow
 
-Now you can associate applications with the user flow.
+Now you'll associate applications with the user flow to enable sign-up for those applications. New users who access the associated applications will be presented with your new self-service sign-up experience.
 
 1. Sign in to the [Azure portal](https://portal.azure.com) as an Azure AD administrator.
 2. Under **Azure services**, select **Azure Active Directory**.
@@ -107,3 +108,4 @@ Now you can associate applications with the user flow.
 - [Add Facebook to your list of social identity providers](facebook-federation.md)
 - [Use API connectors to customize and extend your user flows via web APIs](api-connectors-overview.md)
 - [Add custom approval workflow to your user flow](self-service-sign-up-add-approvals.md)
+- [Learn more about initiating an OAuth 2.0 authorization code flow](../develop/v2-oauth2-auth-code-flow.md#request-an-authorization-code)

articles/active-directory/external-identities/media/self-service-sign-up-user-flow/new-user-flow.png

@@ -7,7 +7,7 @@ manager: amycolannino
 ms.service: active-directory
 ms.topic: how-to
 ms.workload: identity
-ms.date: 06/15/2022
+ms.date: 10/12/2022
 ms.subservice: hybrid
 ms.author: billmath
 
@@ -19,7 +19,7 @@ ms.collection: M365-identity-device-management
 Group writeback allows you to write cloud groups back to your on-premises Active Directory instance by using Azure Active Directory (Azure AD) Connect sync. You can use this feature to manage groups in the cloud, while controlling access to on-premises applications and resources.  
 
 >[NOTE]
->The Group writeback functionality is currently in Public Preview. We are collecting customer feedback and telemetry. Please refer to [the limitations]([#Understand limitations of public preview](https://learn.microsoft.com/azure/active-directory/hybrid/how-to-connect-group-writeback-v2#understand-limitations-of-public-preview) before you enable this funcitonality.
+>The Group writeback functionality is currently in Public Preview as we are collecting customer feedback and telemetry. Please refer to [the limitations](https://learn.microsoft.com/azure/active-directory/hybrid/how-to-connect-group-writeback-v2#understand-limitations-of-public-preview) before you enable this functionality.
 
 
 There are two versions of group writeback. The original version is in general availability and is limited to writing back Microsoft 365 groups to your on-premises Active Directory instance as distribution groups. The new, expanded version of group writeback is in public preview and enables the following capabilities:  
@@ -121,8 +121,8 @@ If you plan to make changes to the default behavior, we recommend that you do so
 
 ## Understand limitations of public preview  
 
-Although this release has undergone extensive testing, you might still encounter issues. One of the goals of this public preview release is to find and fix any issues before the feature moves to general availability. Please also note that any public preview functionality can still receive breaking changes which may require you to make changes to you configuration to continue using this feature. We may also decide to change certain functionality without prior notice.
-Microsoft provides support for this public preview release, but it might not be able to immediately fix issues that you encounter. For these reasons, we recommend that you do not deploy this release in your production environment. 
+Although this release has undergone extensive testing, you might still encounter issues. One of the goals of this public preview release is to find and fix any issues before the feature moves to general availability. Please also note that any public preview functionality can still receive breaking changes which may require you to make changes to you configuration to continue using this feature. We may also decide to change or remove certain functionality without prior notice.
+Microsoft provides support for this public preview release, but we might not be able to immediately fix issues that you encounter. For these reasons, we recommend that you do not deploy this release in your production environment. 
 
 These limitations and known issues are specific to group writeback: 
 

articles/active-directory/external-identities/self-service-sign-up-user-flow.md

@@ -12,7 +12,7 @@ ms.service: azure-netapp-files
 ms.workload: storage
 ms.tgt_pltfrm: na
 ms.topic: how-to
-ms.date: 11/19/2021
+ms.date: 10/13/2022
 ms.author: anfdocs
 ---
 # Deploy the first SAP HANA host using application volume group for SAP HANA
@@ -23,9 +23,6 @@ This article describes how to deploy the first SAP HANA host using Azure NetApp
 
 ## Before you begin
 
-> [!IMPORTANT]
-> Azure NetApp Files application volume group for SAP HANA is currently in preview. You need to submit a waitlist request for accessing the feature through the [**Azure NetApp Files application volume group for SAP HANA waitlist submission page**](https://aka.ms/anfavgpreviewsignup). Wait for an official confirmation email from the Azure NetApp Files team before using application volume group for SAP HANA. 
-
 You should understand the [requirements and considerations for application volume group for SAP HANA](application-volume-group-considerations.md). 
 
 Be sure to follow the **[pinning recommendations](https://aka.ms/HANAPINNING)** and have at least one HANA VM in the availability set started. 

articles/active-directory/hybrid/how-to-connect-group-writeback-v2.md

@@ -12,15 +12,12 @@ ms.service: azure-netapp-files
 ms.workload: storage
 ms.tgt_pltfrm: na
 ms.topic: conceptual
-ms.date: 11/19/2021
+ms.date: 10/13/2022
 ms.author: anfdocs
 ---
 # Understand Azure NetApp Files application volume group for SAP HANA 
 
-This article helps you understand the use cases and key features of Azure NetApp Files application volume group for SAP HANA. 
-
-> [!IMPORTANT]
-> Azure NetApp Files application volume group for SAP HANA is currently in preview. You need to submit a waitlist request for accessing the feature through the [**Azure NetApp Files application volume group for SAP HANA waitlist submission page**](https://aka.ms/anfavgpreviewsignup). Wait for an official confirmation email from the Azure NetApp Files team before using application volume group for SAP HANA. 
+This article helps you understand the use cases and key features of Azure NetApp Files application volume group for SAP HANA.  
 
 Application volume group for SAP HANA enables you to deploy all volumes required to install and operate an SAP HANA database according to best practices. Instead of individually creating the required SAP HANA volumes (including data, log, shared, log-backup, and data-backup volumes), application volume group for SAP HANA creates these volumes in a single "atomic" call. The atomic call ensures that either all volumes or no volumes at all are created.
 

articles/azure-netapp-files/application-volume-group-deploy-first-host.md

@@ -12,13 +12,19 @@ ms.service: azure-netapp-files
 ms.workload: storage
 ms.tgt_pltfrm: na
 ms.topic: overview
-ms.date: 09/07/2022
+ms.date: 10/13/2022
 ms.author: anfdocs
 ---
 # What's new in Azure NetApp Files
 
 Azure NetApp Files is updated regularly. This article provides a summary about the latest new features and enhancements. 
 
+## October 2022
+
+* [Application volume group for SAP HANA](application-volume-group-introduction.md) now generally available (GA)
+
+    The application volume group for SAP HANA feature is now generally available. You no longer need to register the feature to use it. 
+
 ## August 2022
 
 * [Standard network features](configure-network-features.md) are now generally available [in supported regions](azure-netapp-files-network-topologies.md#supported-regions).

articles/azure-netapp-files/application-volume-group-introduction.md

@@ -1,7 +1,7 @@
 ---
 title: Allow the Azure portal URLs on your firewall or proxy server
 description: To optimize connectivity between your network and the Azure portal and its services, we recommend you add these URLs to your allowlist.
-ms.date: 06/29/2022
+ms.date: 10/12/2022
 ms.topic: conceptual
 ---
 
@@ -68,6 +68,7 @@ api.aadrm.com (Azure AD)
 api.loganalytics.io (Log Analytics Service)
 *.applicationinsights.azure.com (Application Insights Service)
 appservice.azure.com (Azure App Services)
+*.arc.azure.net (Azure Arc)
 asazure.windows.net (Analysis Services)
 bastion.azure.com (Azure Bastion Service)
 batch.azure.com (Azure Batch Service)

articles/azure-netapp-files/whats-new.md

@@ -15,19 +15,20 @@ The following table describes the maximum limits for Azure VMware Solution.
 | **Resource** | **Limit** |
 | :-- | :-- |
 | vSphere clusters per private cloud | 12 |
-| Minimum number of ESXi hosts per cluster | 3 |
-| Maximum number of ESXi hosts per cluster | 16 |
+| Minimum number of ESXi hosts per cluster | 3 (hard-limit) |
+| Maximum number of ESXi hosts per cluster | 16 (hard-limit) |
 | Maximum number of ESXi hosts per private cloud | 96 |
-| Maximum number of vCenter Servers per private cloud | 1  |
+| Maximum number of vCenter Servers per private cloud | 1 (hard-limit)  |
 | Maximum number of HCX site pairings | 25 (any edition) |
 | Maximum number of Azure VMware Solution ExpressRoute max linked private clouds | 4<br />The virtual network gateway used determines the actual max linked private clouds.  For more details, see [About ExpressRoute virtual network gateways](../../expressroute/expressroute-about-virtual-network-gateways.md) | 
 | Maximum Azure VMware Solution ExpressRoute port speed | 10 Gbps<br />The virtual network gateway used determines the actual bandwidth. For more details, see [About ExpressRoute virtual network gateways](../../expressroute/expressroute-about-virtual-network-gateways.md) | 
 | Maximum number of Azure Public IPv4 addresses assigned to NSX-T Data Center | 2,000 |
+| Maximum number of Azure VMware Solution Interconnects per private cloud | 10 |
 | vSAN capacity limits | 75% of total usable (keep 25% available for SLA)  |
 | VMware Site Recovery Manager - Maximum number of protected Virtual Machines  | 3,000  |
 | VMware Site Recovery Manager - Maximum number of Virtual Machines per recovery plan  | 2,000  |
 | VMware Site Recovery Manager - Maximum number of protection groups per recovery plan  | 250  |
-| VMware Site Recovery Manager - RPO Values  | 5 min or higher *  |
+| VMware Site Recovery Manager - RPO Values  | 5 min or higher * (hard-limit)  |
 | VMware Site Recovery Manager - Maximum number of virtual machines per protection group  | 500  |
 | VMware Site Recovery Manager - Maximum number of recovery plans  | 250  |