Merge branch 'MicrosoftDocs:main' into krkutser-11-new-markets-withoutTF

Author: krkutser

articles/application-gateway/proxy-buffers.md

@@ -36,9 +36,22 @@ You can keep either the Request or Response buffer, enabled or disable, based on
 > [!WARNING]
 >We strongly recommend that you test and evaluate the performance before rolling this out on the production gateways. 
 
-## How to change the buffer setting? 
+## How to change the buffer settings? 
 
-You can change this setting by using GlobalConfiguration in the ARM template as shown below.
+You can change this setting by using the globalConfiguration property.
+
+### Azure CLI method
+
+**Response Buffer**
+```azurecli-interactive
+az network application-gateway update --name <gw-name> --resource-group <rg-name> --set globalConfiguration.enableResponseBuffering=false
+```
+**Request Buffer**
+```azurecli-interactive
+ az network application-gateway update --name <gw-name> --resource-group <rg-name> --set globalConfiguration.enableRequestBuffering=false
+```
+
+### ARM template method
 
 ```json
 {
@@ -72,5 +85,5 @@ For reference, visit [Azure SDK for .NET](/dotnet/api/microsoft.azure.management
 
 ## Limitations
 - API version 2020-01-01 or later should be used to configure buffers.
-- Currently, these changes are supported only through ARM templates.
+- Currently, these changes are not supported through Portal and PowerShell.
 - Request and Response Buffers can only be disabled for the WAF v2 SKU if request body checking is disabled. Otherwise, Request and Response Buffers cannot be disabled for the WAF v2 SKU.

articles/azure-netapp-files/TOC.yml

@@ -219,6 +219,8 @@
         href: configure-nfs-clients.md
       - name: Convert an NFS volume between NFSv3 and NFSv4.1
         href: convert-nfsv3-nfsv41.md
+      - name: Disable showmount
+        href: disable-showmount.md
     - name: Manage SMB volumes
       items:
       - name: Create an SMB volume

articles/azure-netapp-files/disable-showmount.md

@@ -0,0 +1,53 @@
+---
+title: Disable showmount in Azure NetApp Files | Microsoft Docs
+description: Showmount on NFS clients has historically been how users can see exported file systems on an NFS server. You can disable the showmount if it presents a security concern for your needs.
+services: azure-netapp-files
+documentationcenter: ''
+author: b-ahibbard
+manager: ''
+editor: ''
+
+ms.assetid:
+ms.service: azure-netapp-files
+ms.workload: storage
+ms.tgt_pltfrm: na
+ms.topic: how-to
+ms.date: 03/16/2023
+ms.author: anfdocs
+---
+# Disable showmount in Azure NetApp Files (preview)
+
+Showmount on NFS clients has historically been how users can see exported file systems on an NFS server. By default, Azure NetApp Files enables showmount functionality to show exported paths but doesn't list the allowed client access. Instead, showmount displays that (everyone) has access. The setting allows NFS clients to use the `showmount -e` command to see a list of exports available on the Azure NetApp Files NFS-enabled storage endpoint.
+
+This functionality might cause security scanners to flag the Azure NetApp Files NFS service as having a vulnerability because these scanners often use showmount to see what is being returned. In those scenarios, you might want to disable showmount on Azure NetApp Files.
+
+Some applications, however, make use of showmount for functionality, such as Oracle OVM. In those scenarios, inform the security team of the application requirements.
+
+The disable showmount capability is currently in preview. If you're using this feature for the first time, you need to register the feature first. By registering the feature, you disable the showmount. By unregistering the feature, you enable the showmount. 
+
+1.  Register the feature by running the following commands:
+
+    ```azurepowershell-interactive
+    Register-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFDisableShowmount
+    ```
+
+2. Check the status of the feature registration: 
+
+    > [!NOTE]
+    > The **RegistrationState** may be in the `Registering` state for up to 60 minutes before changing to `Registered`. Wait until the status is `Registered` before continuing.
+
+    ```azurepowershell-interactive
+    Get-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFDisableShowmount
+    ```
+
+    You can also use [Azure CLI commands](/cli/azure/feature) `az feature register` and `az feature show` to register the feature and display the registration status. 
+
+3. Confirm that you've disabled the showmount in the **Overview** menu of your Azure subscription. The attribute **Disable Showmount** displays as true if the operation succeeded.
+
+    :::image type="content" source="../media/azure-netapp-files/disable-showmount.png" alt-text="Screenshot of the Azure interface depicting the disable showmount option." lightbox="../media/azure-netapp-files/disable-showmount.png":::
+
+4. If you need to enable showmount, unregister the feature. 
+ 
+    ```azurepowershell-interactive
+    Unregister-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFDisableShowmount
+    ```

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

@@ -12,7 +12,7 @@ ms.service: azure-netapp-files
 ms.workload: storage
 ms.tgt_pltfrm: na
 ms.topic: overview
-ms.date: 03/01/2023
+ms.date: 03/16/2023
 ms.author: anfdocs
 ---
 # What's new in Azure NetApp Files
@@ -21,6 +21,10 @@ Azure NetApp Files is updated regularly. This article provides a summary about t
 
 ## March 2023
 
+* [Disable showmount](disable-showmount.md) (Preview)
+
+    By default, Azure NetApp Files enables [showmount functionality](/windows-server/administration/windows-commands/showmount) to show NFS exported paths. The setting allows NFS clients tp use the `showmount -e` command to see a list of exports available on the Azure NetApp Files NFS-enabled storage endpoint. This functionality might cause security scanners to flag the Azure NetApp Files NFS service as having a vulnerability because these scanners often use showmount to see what is being returned. In those scenarios, you might want to disable showmount on Azure NetApp Files. This setting allows you to enable/disable showmount for your NFS-enabled storage endpoints. 
+
 * [Active Directory support improvement](create-active-directory-connections.md#preferred-server-ldap) (Preview)
 
     The Preferred server for LDAP client option allows you to submit the IP addresses of up to two Active Directory (AD) servers as a comma-separated list. Rather than sequentially contacting all of the discovered AD services for a domain, the LDAP client will contact the specified servers first. 
@@ -148,6 +152,7 @@ Azure NetApp Files is updated regularly. This article provides a summary about t
     * Azure Managed Disk as an alternate storage back end
 
 * [Active Directory connection enhancement: Reset Active Directory computer account password](create-active-directory-connections.md#reset-active-directory) (Preview)
+>>>>>>> 15252d24ac8fc6f9c2853c1a0deeb10d3393f104
 
 ## June 2022
 

articles/communications-gateway/deploy.md

@@ -5,7 +5,7 @@ author: rcdun
 ms.author: rdunstan
 ms.service: communications-gateway
 ms.topic: how-to 
-ms.date: 12/16/2022
+ms.date: 03/16/2023
 ---
 
 # Deploy Azure Communications Gateway
@@ -55,19 +55,26 @@ Once your resource has been provisioned, a message appears saying **Your deploym
 
 ## 3. Complete the JSON onboarding file
 
-Your onboarding team needs more information to complete your Operator Connect onboarding. If you're being onboarded to Operator Connect or Teams Phone Mobile by Microsoft, the onboarding team will contact you. Fill in the JSON onboarding file and give it to your onboarding team.
+> [!NOTE]
+>This step is required to set you up as an Operator in the Teams Phone Mobile (TPM) and Operator Connect (OC) environments. Skip this step if you have already onboarded to TPM or OC.
 
-Wait for your onboarding team to confirm that the onboarding process is complete before testing your portal access.
+Before your onboarding team can finish onboarding you to the Operator Connect and/or Teams Phone Mobile environments, you need to provide them with some additional information.
+
+1. Wait for your onboarding team to provide you with a form to collect the additional information. 
+1. Complete the form and give it to your onboarding team.
+1. Wait for your onboarding team to confirm that the onboarding process is complete before testing your portal access.
+
+If you don't already have an onboarding team, contact [email protected], providing your Azure subscription ID and contact details.
 
 ## 4. Test your portal access
 
-Navigate to the [Operator Connect homepage](https://operatorconnect.microsoft.com/) and ensure you're able to sign in.
+Navigate to the [Operator Connect homepage](https://operatorconnect.microsoft.com/) and check that you're able to sign in.
 
 ## 5. Register your deployment's domain name in Active Directory
 
 Microsoft Teams only sends traffic to domains that you've confirmed that you own. Your Azure Communications Gateway deployment automatically receives an autogenerated fully qualified domain name (FQDN). You need to add this domain name to your Active Directory tenant as a custom domain name, share the details with your onboarding team and then verify the domain name. This process confirms that you own the domain.
 
-1. Navigate to your Azure Communications Gateway resource and select **Properties**. You'll see a field named **Domain name**. This name is your deployment's domain name.
+1. Navigate to your Azure Communications Gateway resource and select **Properties**. Find the field named **Domain name**. This name is your deployment's domain name.
 1. Complete the following procedure: [Add your custom domain name to Azure AD](../active-directory/fundamentals/add-custom-domain.md#add-your-custom-domain-name-to-azure-ad).
 1. Share your DNS TXT record information with your onboarding team. Wait for your onboarding team to confirm that the DNS TXT record has been configured correctly.
 1. Complete the following procedure: [Verify your custom domain name](../active-directory/fundamentals/add-custom-domain.md#verify-your-custom-domain-name).