Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into semcache2

Author: dlepow

articles/app-service/overview-access-restrictions.md

@@ -26,12 +26,16 @@ You have the option of configuring a set of access restriction rules for each si
 
 App access allows you to configure if access is available through the default (public) endpoint. You configure this behavior to either be `Disabled` or `Enabled`. When access is enabled, you can add [Site access](#site-access) restriction rules to control access from select virtual networks and IP addresses.
 
-If the setting isn't set (the property is `null`), the default behavior is to enable access unless a private endpoint exists which changes the behavior to disable access. In Azure portal, when the property isn't set, the radio button is also not set and you're then using default behavior.
+If the setting isn't set (the property is `null`), the default behavior is to enable access unless a private endpoint exists which changes the behavior to disable access. In the Azure portal, when the property isn't set, the radio button is also not set and you're then using default behavior.
 
 :::image type="content" source="media/overview-access-restrictions/app-access-portal.png" alt-text="Screenshot of app access option in Azure portal.":::
 
 In the Azure Resource Manager API, the property controlling app access is called `publicNetworkAccess`. For internal load balancer (ILB) App Service Environment, the default entry point for apps is always internal to the virtual network. Enabling app access (`publicNetworkAccess`) doesn't grant direct public access to the apps; instead, it allows access from the default entry point, which corresponds to the internal IP address of the App Service Environment. If you disable app access on an ILB App Service Environment, you can only access the apps through private endpoints added to the individual apps.
 
+> [!NOTE]
+> For Linux sites, changes to the `publicNetworkAccess` property trigger app restarts. 
+> 
+
 ## Site access
 
 Site access restrictions let you filter the incoming requests. Site access restrictions allow you to build a list of allow and deny rules that are evaluated in priority order. It's similar to the network security group (NSG) feature in Azure networking.

articles/azure-netapp-files/azure-netapp-files-resize-capacity-pools-or-volumes.md

@@ -17,12 +17,13 @@ For information about monitoring a volume’s capacity, see [Monitor the capacit
 
 ## Considerations
 
+* Resize operations on Azure NetApp Files volumes don't result in data loss.
 * Volume quotas are indexed against `maxfiles` limits. Once a volume has surpassed a `maxfiles` limit, you cannot reduce the volume size below the quota that corresponds to that `maxfiles` limit. For more information and specific limits, see [`maxfiles` limits](azure-netapp-files-resource-limits.md#maxfiles-limits-).
 * Capacity pools with Basic network features have a minimum size of 4 TiB. For capacity pools with Standard network features, the minimum size is 1 TiB. For more information, see [Resource limits](azure-netapp-files-resource-limits.md)
 * Volume resize operations are nearly instantaneous but not always immediate. There can be a short delay for the volume's updated size to appear in the portal. Verify the size from a host perspective before re-attempting the resize operation.
 
 >[!IMPORTANT]
->If you are using a capacity pool with a size of 2 TiB or smaller and have `ANFStdToBasicNetworkFeaturesRevert` and `ANFBasicToStdNetworkFeaturesUpgrade` AFECs enabled and want to change the capacity pool's QoS type from auto manual, you must [perform the operation with the REST API](#resizing-the-capacity-pool-or-a-volume-using-rest-api) using the `2023-07-01` API version or later.
+>If you are using a capacity pool with a size of 2 TiB or smaller and have `ANFStdToBasicNetworkFeaturesRevert` and `ANFBasicToStdNetworkFeaturesUpgrade` AFECs enabled and want to change the capacity pool's QoS type from auto to manual, you must [perform the operation with the REST API](#resizing-the-capacity-pool-or-a-volume-using-rest-api) using the `2023-07-01` API version or later.
 
 ## Resize the capacity pool using the Azure portal 
 

articles/azure-netapp-files/backup-configure-policy-based.md

@@ -30,6 +30,8 @@ A backup policy enables a volume to be protected on a regularly scheduled interv
 
 You need to create a backup policy and associate the backup policy to the volume that you want to back up. A single backup policy can be attached to multiple volumes. Backups can be temporarily suspended by disabling the policy. A backup policy can't be deleted if it's attached to any volumes.
 
+Before creating the policy, review [Azure NetApp Files resource limits](azure-netapp-files-resource-limits.md).    
+
 To enable a policy-based (scheduled) backup: 
 
 1. Sign in to the Azure portal and navigate to **Azure NetApp Files**. 

articles/azure-netapp-files/media/azure-netapp-files-understand-storage-hierarchy/azure-netapp-files-storage-hierarchy.png

@@ -22,18 +22,6 @@ If you're interested in providing feedback or working closely on your migration
 
 - An Azure subscription. [!INCLUDE [quickstarts-free-trial-note](~/reusable-content/ce-skilling/azure/includes/quickstarts-free-trial-note.md)]
 - Ensure the Azure identity you use to sign in has either the [Contributor](/azure/role-based-access-control/built-in-roles#contributor) role or the [Owner](/azure/role-based-access-control/built-in-roles#owner) role in the current subscription. For an overview of Azure roles, see [What is Azure role-based access control (Azure RBAC)?](/azure/role-based-access-control/overview)
-- Ensure you have the necessary Red Hat licenses. You need to have a Red Hat Account with Red Hat Subscription Management (RHSM) entitlement for JBoss EAP. This entitlement lets the Azure portal install the Red Hat tested and certified JBoss EAP version.
-  > [!NOTE]
-  > If you don't have an EAP entitlement, you can sign up for a free developer subscription through the [Red Hat Developer Subscription for Individuals](https://developers.redhat.com/register). Save aside the account details, which you use as the *RHSM username* and *RHSM password* in the next section.
-- After you're registered, you can find the necessary credentials (*Pool IDs*) by using the following steps. You also use the *Pool IDs* as the *RHSM Pool ID with EAP entitlement* later in this article.
-  1. Sign in to your [Red Hat account](https://sso.redhat.com).
-  1. The first time you sign in, you're asked to complete your profile. Make sure you select **Personal** for **Account Type**, as shown in the following screenshot.
-
-     :::image type="content" source="media/jboss-eap-azure-vm/update-account-type-as-personal.png" alt-text="Screenshot of the Red Hat profile Update Your Account page." lightbox="media/jboss-eap-azure-vm/update-account-type-as-personal.png":::
-
-  1. In the tab where you're signed in, open [Red Hat Developer Subscription for Individuals](https://aka.ms/red-hat-individual-dev-sub). This link takes you to all of the subscriptions in your account for the appropriate SKU.
-  1. Select the first subscription from the **All purchased Subscriptions** table.
-  1. Copy and save aside the value following **Master Pools** from **Pool IDs**.
 - A Java Development Kit (JDK), version 11. In this guide, we recommend the [Red Hat Build of OpenJDK](https://developers.redhat.com/products/openjdk/download). Ensure that your `JAVA_HOME` environment variable is set correctly in the shells in which you run the commands.
 - [Git](https://git-scm.com/downloads). Use `git --version` to test whether `git` works. This tutorial was tested with version 2.34.1.
 - [Maven](https://maven.apache.org/download.cgi). Use `mvn -version` to test whether `mvn` works. This tutorial was tested with version 3.8.6.
@@ -135,9 +123,6 @@ The following steps show you how to fill out the **JBoss EAP Settings** pane sho
 1. Leave the default value **jbossadmin** for **JBoss EAP Admin username**.
 1. Provide a JBoss EAP password for **JBoss EAP password**. Use the same value for **Confirm password**. Save aside the value for later use.
 1. Leave the default option **No** for **Connect to an existing Red Hat Satellite Server?**.
-1. Provide your RHSM username for **RHSM username**. The value is the same one that was prepared in the prerequisites section.
-1. Provide your RHSM password for **RHSM password**. Use the same value for **Confirm password**. The value is the same one that was prepared in the prerequisites section.
-1. Provide your RHSM pool ID for **RHSM Pool ID with EAP entitlement**. The value is the same one that was prepared in the prerequisites section.
 1. Select **Next: Azure Application Gateway**.
 
 The following steps show you how to fill out the **Azure Application Gateway** pane shown in the following screenshot.