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

Author: duongau

articles/app-service/toc.yml

@@ -25,8 +25,6 @@
       href: quickstart-python.md
     - name: Deploy WordPress
       href: quickstart-wordpress.md
-    - name: Deploy Go (experimental)
-      href: quickstart-golang.md
     - name: Deploy a custom container
       href: quickstart-custom-container.md
     - name: Use ARM template

articles/azure-arc/servers/troubleshoot-agent-onboard.md

@@ -104,16 +104,13 @@ The following table lists some of the known errors and suggestions on how to tro
 |--------|------|---------------|---------|
 |Failed to acquire authorization token device flow |`Error occurred while sending request for Device Authorization Code: Post https://login.windows.net/fb84ce97-b875-4d12-b031-ef5e7edf9c8e/oauth2/devicecode?api-version=1.0:  dial tcp 40.126.9.7:443: connect: network is unreachable.` |Can't reach `login.windows.net` endpoint | Run [azcmagent check](azcmagent-check.md) to see if a firewall is blocking access to Microsoft Entra ID. |
 |Failed to acquire authorization token device flow |`Error occurred while sending request for Device Authorization Code: Post https://login.windows.net/fb84ce97-b875-4d12-b031-ef5e7edf9c8e/oauth2/devicecode?api-version=1.0:  dial tcp 40.126.9.7:443: connect: network is Forbidden`. |Proxy or firewall is blocking access to `login.windows.net` endpoint. | Run [azcmagent check](azcmagent-check.md) to see if a firewall is blocking access to Microsoft Entra ID.|
-|Failed to acquire authorization token device flow  |`Error occurred while sending request for Device Authorization Code: Post https://login.windows.net/fb84ce97-b875-4d12-b031-ef5e7edf9c8e/oauth2/devicecode?api-version=1.0:  dial tcp lookup login.windows.net: no such host`. | Group Policy Object *Computer Configuration\ Administrative Templates\ System\ User Profiles\ Delete user profiles older than a specified number of days on system restart* is enabled. | Verify the GPO is enabled and targeting the affected machine. See footnote <sup>[1](#footnote1)</sup> for further details. |
 |Failed to acquire authorization token from SPN |`Failed to execute the refresh request. Error = 'Post https://login.windows.net/fb84ce97-b875-4d12-b031-ef5e7edf9c8e/oauth2/token?api-version=1.0: Forbidden'` |Proxy or firewall is blocking access to `login.windows.net` endpoint. |Run [azcmagent check](azcmagent-check.md) to see if a firewall is blocking access to Microsoft Entra ID. |
 |Failed to acquire authorization token from SPN |`Invalid client secret is provided` |Wrong or invalid service principal secret. |Verify the service principal secret. |
 | Failed to acquire authorization token from SPN |`Application with identifier 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx' wasn't found in the directory 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx'. This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant` |Incorrect service principal and/or Tenant ID. |Verify the service principal and/or the tenant ID.|
 |Get ARM Resource Response |`The client '[email protected]' with object id 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx' does not have authorization to perform action 'Microsoft.HybridCompute/machines/read' over scope '/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/resourcegroups/myResourceGroup/providers/Microsoft.HybridCompute/machines/MSJC01' or the scope is invalid. If access was recently granted, please refresh your credentials."}}" Status Code=403` |Wrong credentials and/or permissions |Verify you or the service principal is a member of the **Azure Connected Machine Onboarding** role. |
 |Failed to AzcmagentConnect ARM resource |`The subscription isn't registered to use namespace 'Microsoft.HybridCompute'` |Azure resource providers aren't registered. |Register the [resource providers](prerequisites.md#azure-resource-providers). |
 |Failed to AzcmagentConnect ARM resource |`Get https://management.azure.com/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/resourcegroups/myResourceGroup/providers/Microsoft.HybridCompute/machines/MSJC01?api-version=2019-03-18-preview:  Forbidden` |Proxy server or firewall is blocking access to `management.azure.com` endpoint. | Run [azcmagent check](azcmagent-check.md) to see if a firewall is blocking access to Azure Resource Manager. |
 
-<a name="footnote1"></a><sup>1</sup>If this GPO is enabled and applies to machines with the Connected Machine agent, it deletes the user profile associated with the built-in account specified for the *himds* service. As a result, it also deletes the authentication certificate used to communicate with the service that is cached in the local certificate store for 30 days. Before the 30-day limit, an attempt is made to renew the certificate. To resolve this issue, follow the steps to [disconnect the agent](azcmagent-disconnect.md) and then re-register it with the service running `azcmagent connect`.
-
 ## Next steps
 
 If you don't see your problem here or you can't resolve your issue, try one of the following channels for more support:

articles/azure-netapp-files/TOC.yml

@@ -447,6 +447,8 @@
       href: azacsnap-cmd-ref-runbefore-runafter.md
 - name: Resources
   items:
+  - name: Azure NetApp Files tools 
+    href: tools-reference.md
   - name: Pricing
     href: https://azure.microsoft.com/pricing/details/netapp/
   - name: Regional availability

articles/azure-netapp-files/azure-government.md

@@ -34,7 +34,7 @@ All [Azure NetApp Files features](whats-new.md) available on Azure public cloud
 | Azure NetApp Files backup | Public preview | No |
 | Azure NetApp Files large volumes | Public preview | No |
 | Edit network features for existing volumes | Public preview | No |
-| Standard storage with cool access in Azure NetApp Files | Public preview | No |
+| Standard storage with cool access in Azure NetApp Files | Public preview | Public preview [(in select regions)](cool-access-introduction.md#supported-regions) |
 
 ## Portal access
 

articles/azure-netapp-files/cool-access-introduction.md

@@ -57,6 +57,7 @@ Standard storage with cool access is supported for the following regions:
 * Switzerland North 
 * Switzerland West 
 * UAE North 
+* US Gov Arizona
 * West US
 
 ## Effects of cool access on data

articles/azure-netapp-files/tools-reference.md

@@ -0,0 +1,53 @@
+---
+title: Azure NetApp Files tools 
+description: Learn about the tools available to you to maximize your experience and savings with Azure NetApp Files. 
+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: conceptual
+ms.date: 01/12/2023
+ms.author: anfdocs
+---
+
+# Azure NetApp Files tools 
+
+Azure NetApp Files offers [multiple tools](https://azure.github.io/azure-netapp-files/) to estimate costs, understand features and availability, and monitor your Azure NetApp Files deployment.
+
+* [**Azure NetApp Files Performance Calculator**](https://aka.ms/anfcalc)
+
+    The Azure NetApp Files Performance Calculator enables you to easily calculate the performance and estimated cost of a volume based on the size and service level or performance requirements. It also helps you estimate backup and replication costs.
+
+* [**Azure NetApp Files datastore for Azure VMware Solution TCO Estimator**](https://aka.ms/anfavscalc)
+
+    This tool assists you with sizing an Azure VMware Solution. In the Estimator, provide the details of your current VMware environment to learn how much you can save by using Azure NetApp Files datastores.
+
+* [**SAP on Azure NetApp Files Sizing Estimator**](https://aka.ms/anfsapcalc)
+
+    This comprehensive tool estimates the infrastructure costs of an SAP HANA on Azure NetApp Files landscape. The estimate includes primary storage, backup, and replication costs.
+
+* [**Azure NetApp Files Standard storage with cool access cost savings estimator**](https://aka.ms/anfcoolaccesscalc)
+
+    Standard storage with cool access enables you to transparently move infrequently accessed data to less expensive storage. This cost savings estimator helps you understand how much money you can save by enabling Standard storage with cool access.
+
+* [**Azure NetApp Files Region and Feature Map**](https://aka.ms/anfmap)
+    
+    Use this interactive map to understand which regions support Azure NetApp Files and its numerous features. 
+
+* [**Azure NetApp Files on YouTube**](https://www.youtube.com/@azurenetappfiles)
+
+    Learn about the latest features in Azure NetApp Files and watch detailed how-to videos on the Azure NetApp Files YouTube channel. 
+
+* [**ANFCapacityManager**](https://github.com/ANFTechTeam/ANFCapacityManager)
+
+    ANFCapacityManager is an Azure logic application that automatically creates metric alert rules in Azure Monitor to notify you when volumes are approaching their capacity. Optionally, it can increase the volumes' sizes automatically to keep your applications online.
+
+* [**ANFHealthCheck**](https://github.com/seanluce/ANFHealthCheck)
+
+    ANFHeathCheck is a PowerShell runbook that generates artful HTML reports of your entire Azure NetApp Files landscape. Optionally, it can automatically reduce over-sized volumes and capacity pools to reduce your TCO.

articles/energy-data-services/concepts-authentication.md

@@ -1,6 +1,6 @@
 ---
 title: Authentication concepts in Microsoft Azure Data Manager for Energy 
-description:  This article describes the various concepts regarding the authentication in Azure Data Manager for Energy.
+description: This article describes various concepts of authentication in Azure Data Manager for Energy.
 author: shikhagarg1
 ms.author: shikhagarg
 ms.service: energy-data-services
@@ -9,21 +9,26 @@ ms.date: 02/10/2023
 ms.custom: template-concept
 ---
 
-# Authentication concepts in Azure Data Manager for Energy 
-Authentication confirms the identity of the users. The access flows can be user triggered, system triggered, or system API communication. In this article, you learn about service principals and authorization token.
+# Authentication concepts in Azure Data Manager for Energy
+
+Authentication confirms the identity of users. The access flows can be user triggered, system triggered, or system API communication. In this article, you learn about service principals and authorization tokens.
 
 ## Service principals
-In the Azure Data Manager for Energy instance, 
-1. No Service Principals are created. 
-2. The app-id is used for API access. The same app-id is used to provision ADME instance.
-3. The app-id doesn't have access to infrastructure resources. 
-4. The app-id also gets added as OWNER to all OSDU groups by default. 
-5. For service-to-service (S2S) communication, ADME uses MSI (Microsoft Service Identity).
-
-In the OSDU instance, 
-1. Terraform scripts create two Service Principals: 
-   1. The first Service Principal is used for API access. It can also manage infrastructure resources. 
-   2. The second Service Principal is used for service-to-service (S2S) communications. 
-
-## Generate authorization token
-You can generate the authorization token using the steps outlined in [Generate auth token](how-to-generate-auth-token.md). 
+
+In an Azure Data Manager for Energy instance:
+
+- No service principals are created.
+- The app ID is used for API access. The same app ID is used to provision an Azure Data Manager for Energy instance.
+- The app ID doesn't have access to infrastructure resources.
+- The app ID also gets added as OWNER to all OSDU groups by default.
+- For service-to-service communication, Azure Data Manager for Energy uses Managed Service Identity.
+
+In an OSDU instance:
+
+- Terraform scripts create two service principals:
+   - The first service principal is used for API access. It can also manage infrastructure resources.
+   - The second service principal is used for service-to-service communications.
+
+## Generate an authorization token
+
+To generate the authorization token, follow the steps in [Generate auth token](how-to-generate-auth-token.md).