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

asudbring · asudbring · commit 5d51fc91fe05 · 2024-08-19T15:07:37.000-05:00
diff --git a/CODEOWNERS b/CODEOWNERS
@@ -16,6 +16,6 @@
 /articles/mysql @tynevi @thomps23
 /articles/managed-instance-apache-cassandra @tynevi @thomps23
 /articles/virtual-machines @jasonwhowell @thomps23
-/articles/virtual-machines-scale-set @jasonwhowell @thomps23
+/articles/virtual-machines-scale-sets @jasonwhowell @thomps23
 /articles/container-instances @jasonwhowell @thomps23
 /articles/service-fabric @jasonwhowell @thomps23
diff --git a/articles/azure-functions/functions-reference.md b/articles/azure-functions/functions-reference.md
@@ -163,12 +163,12 @@ For example, the `connection` property for an Azure Blob trigger definition migh
 
 ### Configure an identity-based connection
 
-Some connections in Azure Functions can be configured to use an identity instead of a secret. Support depends on the extension using the connection. In some cases, a connection string may still be required in Functions even though the service to which you're connecting supports identity-based connections. For a tutorial on configuring your function apps with managed identities, see the [creating a function app with identity-based connections tutorial](./functions-identity-based-connections-tutorial.md).
-
+Some connections in Azure Functions can be configured to use an identity instead of a secret. Support depends on the runtime version and the extension using the connection. In some cases, a connection string may still be required in Functions even though the service to which you're connecting supports identity-based connections. For a tutorial on configuring your function apps with managed identities, see the [creating a function app with identity-based connections tutorial](./functions-identity-based-connections-tutorial.md).
 
 > [!NOTE]
 > When running in a Consumption or Elastic Premium plan, your app uses the [`WEBSITE_AZUREFILESCONNECTIONSTRING`](functions-app-settings.md#website_contentazurefileconnectionstring) and [`WEBSITE_CONTENTSHARE`](functions-app-settings.md#website_contentshare) settings when connecting to Azure Files on the storage account used by your function app. Azure Files doesn't support using managed identity when accessing the file share. For more information, see [Azure Files supported authentication scenarios](../storage/files/storage-files-active-directory-overview.md#supported-authentication-scenarios)
 
+Identity-based connections are only supported on Functions 4.x, If you are using version 1.x, you must first [migrate to version 4.x](./migrate-version-1-version-4.md).
 
 The following components support identity-based connections:
 
@@ -255,6 +255,15 @@ An identity-based connection for an Azure service accepts the following common p
 
 Other options may be supported for a given connection type. Refer to the documentation for the component making the connection.
 
+##### Azure SDK Environment Variables
+
+> [!CAUTION]
+> Use of the Azure SDK's [`EnvironmentCredential`][environment-credential] environment variables is not recommended due to the potentially unintentional impact on other connections. They also are not fully supported when deployed to Azure Functions.
+
+The environment variables associated with the Azure SDK's [`EnvironmentCredential`][environment-credential] can also be set, but these are not processed by the Functions service for scaling in Consumption plans. These environment variables are not specific to any one connection and will apply as a default unless a corresponding property is not set for a given connection. For example, if `AZURE_CLIENT_ID` is set, this would be used as if `<CONNECTION_NAME_PREFIX>__clientId` had been configured. Explicitly setting `<CONNECTION_NAME_PREFIX>__clientId` would override this default.
+
+[environment-credential]: /dotnet/api/azure.identity.environmentcredential
+
 ##### Local development with identity-based connections
 
 > [!NOTE]
diff --git a/articles/azure-netapp-files/snapshots-delete.md b/articles/azure-netapp-files/snapshots-delete.md
@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 09/16/2021
+ms.date: 03/16/2024
 ms.author: anfdocs
 ---
 
diff --git a/articles/azure-netapp-files/snapshots-edit-hide-path.md b/articles/azure-netapp-files/snapshots-edit-hide-path.md
@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 09/16/2021
+ms.date: 03/16/2024
 ms.author: anfdocs
 ---
 
diff --git a/articles/azure-netapp-files/snapshots-introduction.md b/articles/azure-netapp-files/snapshots-introduction.md
@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: conceptual
-ms.date: 11/22/2022
+ms.date: 06/03/2024
 ms.author: anfdocs
 ---
 # How Azure NetApp Files snapshots work
diff --git a/articles/azure-netapp-files/snapshots-manage-policy.md b/articles/azure-netapp-files/snapshots-manage-policy.md
@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 05/18/2023
+ms.date: 03/18/2024
 ms.author: anfdocs
 ---
 
diff --git a/articles/azure-netapp-files/snapshots-restore-file-client.md b/articles/azure-netapp-files/snapshots-restore-file-client.md
@@ -6,7 +6,7 @@ author: b-hchen
 ms.service: azure-netapp-files
 ms.custom: linux-related-content
 ms.topic: how-to
-ms.date: 09/16/2021
+ms.date: 03/16/2024
 ms.author: anfdocs
 ---
 
diff --git a/articles/azure-netapp-files/snapshots-restore-file-single.md b/articles/azure-netapp-files/snapshots-restore-file-single.md
@@ -5,13 +5,13 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 05/04/2023
+ms.date: 03/04/2024
 ms.author: anfdocs
 ---
 
 # Restore individual files using single-file snapshot restore 
 
-If you do not want to [restore the entire snapshot to a new volume](snapshots-restore-new-volume.md) or [copy large files across the network](snapshots-restore-file-client.md), you can use the single-file snapshot restore feature to recover individual files directly within a volume from a snapshot. This option does not require an external client data copy.  
+If you don't want to [restore the entire snapshot to a new volume](snapshots-restore-new-volume.md) or [copy large files across the network](snapshots-restore-file-client.md), you can use the single-file snapshot restore feature to recover individual files directly within a volume from a snapshot. This option doesn't require an external client data copy.  
 
 The single-file snapshot restore feature enables you to restore a single file or a list of files (up to 10 files at a time) from a snapshot. You can specify a specific destination location or folder for the files to be restored to.    
 
@@ -20,8 +20,8 @@ The single-file snapshot restore feature enables you to restore a single file or
 * If you use this feature to restore files to be new files, ensure that the volume has enough logical free space to accommodate the files.
 * You can restore up to 10 files at a time, specified in a total length of 1024 characters.    
 * All the directories in the destination path that you specify must be present in the active file system. 
-The restore operation does not create directories in the process. If the specified destination path is invalid (doesn't exist in Active file system), the restore operation will fail.
-* If you don’t specify a destination path, the files will be restored to the original file location. If the files already exist in the original location, they will be overwritten by the files restored from the snapshot. 
+The restore operation doesn't create directories in the process. If the specified destination path is invalid (doesn't exist in Active file system), the restore operation will fail.
+* If you don’t specify a destination path, the files restore to the original file location. If the files already exist in the original location, they are overwritten by the files restored from the snapshot. 
 * A volume can have only one active file-restore operation. If you want to restore additional files, you must wait until the current restore operation is complete before triggering another restore operation.   
 * *During the file restore operation*, the following restrictions apply: 
     * You can't create new snapshots on the volume.  
@@ -32,9 +32,9 @@ The restore operation does not create directories in the process. If the specifi
 
 1. Navigate to the volume that has the snapshot to use for restoring files.    
 
-2. Click **Snapshots** to display the list of volume snapshots.
+2. Select **Snapshots** to display the list of volume snapshots.
 
-3. Right-click the snapshot that you want to use for restoring files, and then select **Restore Files** from the menu.
+3. Right-click the snapshot that you want to use for restoring files, then select **Restore Files** from the menu.
 
     [ ![Snapshot that shows how to access the Restore Files menu item.](./media/snapshots-restore-file-single/snapshot-restore-files-menu.png) ](./media/snapshots-restore-file-single/snapshot-restore-files-menu.png#lightbox)
 
@@ -45,14 +45,14 @@ The restore operation does not create directories in the process. If the specifi
         * Regardless of the volume’s protocol type (NFS, SMB, or dual protocol), directories in the path must be specified using forward slashes (`/`) and not backslashes (`\`).  
 
     2. In the **Destination Path** field, provide the location in the volume where the specified files are to be restored to.
-        * If you don’t specify a destination path, the files are restored to their original location. If files with the same names already exist in the original location, they are overwritten by the files restored from the snapshot.  
+        * If you don’t specify a destination path, the files are restored to their original location. If files with the same names already exist in the original location, they're overwritten by the files restored from the snapshot.  
         * If you specify a destination path: 
             * Ensure that all directories in the path are present in the active file system.  Otherwise, the restore operation fails.   
                 For example, if you specify `/CurrentCopy/contoso` as the destination path, the `/CurrentCopy/contoso` path must already exist.  
             * By specifying a destination path, all files specified in the File Paths field are restored to the destination path (folder).
             * Regardless of the volume’s protocol type (NFS, SMB, or dual protocol), directories in the path must be specified using forward slashes (`/`) and not backslashes (`\`).   
 
-    3. Click **Restore** to begin the restore operation.
+    3. Select **Restore** to initiate the restore operation.
 
     ![Snapshot the Restore Files window.](./media/snapshots-restore-file-single/snapshot-restore-files-window.png)
 
@@ -86,8 +86,8 @@ The path `/volume-azure-nfs/currentCopy/contoso` must be valid in the active fil
 
 From the Azure portal:   
 
-1. Click **Snapshots**. Right-click the snapshot `daily-10-min-past-12am.2021-09-08_0010`.
-2. Click **Restore Files**.
+1. Select **Snapshots**. Right-click the snapshot `daily-10-min-past-12am.2021-09-08_0010`.
+2. Select **Restore Files**.
 3. Specify **`/contoso/vm-8976.vmdk`** in File Paths.
 4. Specify **`/currentCopy/contoso`** in Destination Path.
 
@@ -127,8 +127,8 @@ Destination path in the active file system:
 The path `N:\currentCopy\contoso` must be valid in the active file system.
 
 From the Azure portal: 
-1. Click **Snapshots**. Select the snapshot `daily-10-min-past-12am.2021-09-08_0010`.
-2. Click **Restore Files**.
+1. Select **Snapshots**. Select the snapshot `daily-10-min-past-12am.2021-09-08_0010`.
+2. Select **Restore Files**.
 3. Specify **`/contoso/vm-9981.vmdk`** in File Paths.
 4. Specify **`/currentCopy/contoso`** in Destination Path.
 
diff --git a/articles/azure-netapp-files/snapshots-restore-new-volume.md b/articles/azure-netapp-files/snapshots-restore-new-volume.md
@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 02/22/2023
+ms.date: 03/22/2024
 ms.author: anfdocs
 ---
 
diff --git a/articles/azure-netapp-files/snapshots-revert-volume.md b/articles/azure-netapp-files/snapshots-revert-volume.md
@@ -5,13 +5,13 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 02/28/2023
+ms.date: 03/28/2024
 ms.author: anfdocs
 ---
 
 # Revert a volume using snapshot revert with Azure NetApp Files
 
-The [snapshot](snapshots-introduction.md) revert functionality enables you to quickly revert a volume to the state it was in when a particular snapshot was taken. In most cases, reverting a volume is much faster than restoring individual files from a snapshot to the active file system. It is also more space efficient compared to restoring a snapshot to a new volume. 
+The [snapshot](snapshots-introduction.md) revert functionality enables you to quickly revert a volume to the state it was in when a particular snapshot was taken. In most cases, reverting a volume is faster than restoring individual files from a snapshot to the active file system. It's also more space efficient compared to restoring a snapshot to a new volume. 
 
 You can find the Revert Volume option in the Snapshots menu of a volume. After you select a snapshot for reversion, Azure NetApp Files reverts the volume to the data and timestamps that it contained when the selected snapshot was taken. 
 
@@ -22,7 +22,7 @@ The revert functionality is also available in configurations with volume replica
 
 ## Considerations
 
-* Reverting a volume using snapshot revert is not supported on [Azure NetApp Files volumes that have backups](backup-requirements-considerations.md). 
+* Reverting a volume using snapshot revert isn't supported on [Azure NetApp Files volumes that have backups](backup-requirements-considerations.md). 
 * In configurations with a volume replication relationship, a SnapMirror snapshot is created to synchronize between the source and destination volumes. This snapshot is created in addition to any user-created snapshots. **When reverting a source volume with an active volume replication relationship, only snapshots that are more recent than this SnapMirror snapshot can be used in the revert operation.** 
 
 ## Steps
@@ -31,8 +31,7 @@ The revert functionality is also available in configurations with volume replica
 
     ![Screenshot that describes the right-click menu of a snapshot.](./media/shared/snapshot-right-click-menu.png) 
 
-2. In the Revert Volume to Snapshot window, 
-type the name of the volume, and click **Revert**.   
+2. In the Revert Volume to Snapshot window, enter the name of the volume then select **Revert**.   
 
     The volume is now restored to the point in time of the selected snapshot.
 
diff --git a/articles/azure-netapp-files/terraform-manage-volume.md b/articles/azure-netapp-files/terraform-manage-volume.md
@@ -6,7 +6,7 @@ author: b-ahibbard
 ms.service: azure-netapp-files
 ms.custom: devx-track-terraform
 ms.topic: how-to
-ms.date: 12/20/2023
+ms.date: 03/20/2024
 ms.author: anfdocs
 ---
 # Update Terraform-managed Azure resources outside of Terraform
diff --git a/articles/azure-vmware/azure-vmware-solution-platform-updates.md b/articles/azure-vmware/azure-vmware-solution-platform-updates.md
@@ -11,6 +11,10 @@ ms.date: 6/12/2024
 
 Microsoft regularly applies important updates to the Azure VMware Solution for new features and software lifecycle management. You should receive a notification through Azure Service Health that includes the timeline of the maintenance. For more information, see [Host maintenance and lifecycle management](architecture-private-clouds.md#host-maintenance-and-lifecycle-management).
 
+## August 2024
+
+All new Azure VMware Solution private clouds are being deployed with VMware vSphere 8.0 version. [Learn more](/azure/azure-vmware/architecture-private-clouds)
+
 ## May 2024
 
 Azure VMware Solution is now generally available in the Central India, UAE North, and Italy North regions, increasing the total region count to 33. [Learn more](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=azure-vmware&rar=true&regions=all)
diff --git a/articles/communication-services/concepts/telephony/direct-routing-provisioning.md b/articles/communication-services/concepts/telephony/direct-routing-provisioning.md
@@ -86,7 +86,7 @@ If you created one voice route with a pattern `^\+1(425|206)(\d{7})$` and added
 If you created one voice route with a pattern `^\+1(425|206)(\d{7})$` and added `sbc1.contoso.biz` and `sbc2.contoso.biz` to it, and then created a second route with the same pattern with `sbc3.contoso.biz` and `sbc4.contoso.biz`. In this case, when the user makes a call to `+1 425 XXX XX XX` or `+1 206 XXX XX XX`, the call is first routed to SBC `sbc1.contoso.biz` or `sbc2.contoso.biz`. If both sbc1 and sbc2 are unavailable, the route with lower priority is tried (`sbc3.contoso.biz` and `sbc4.contoso.biz`). If none of the SBCs of the second route are available, the call is dropped.
 
 ### Three routes example:
-If you created one voice route with a pattern `^\+1(425|206)(\d{7})$` and added `sbc1.contoso.biz` and `sbc2.contoso.biz` to it, and then created a second route with the same pattern with `sbc3.contoso.biz` and `sbc4.contoso.biz`, and created a third route with `^+1(\d[10])$` with `sbc5.contoso.biz`. In this case, when the user makes a call to `+1 425 XXX XX XX` or `+1 206 XXX XX XX`, the call is first routed to SBC `sbc1.contoso.biz` or `sbc2.contoso.biz`. If both sbc1 nor sbc2 are unavailable, the route with lower priority is tried (`sbc3.contoso.biz` and `sbc4.contoso.biz`). If none of the SBCs of a second route are available, the third route is tried. If sbc5 is also not available, the call is dropped. Also, if a user dials `+1 321 XXX XX XX`, the call goes to `sbc5.contoso.biz`, and it isn't available, the call is dropped.
+If you created one voice route with a pattern `^\+1(425|206)(\d{7})$` and added `sbc1.contoso.biz` and `sbc2.contoso.biz` to it, and then created a second route with the same pattern with `sbc3.contoso.biz` and `sbc4.contoso.biz`, and created a third route with `^\+1(\d{10})$` with `sbc5.contoso.biz`. In this case, when the user makes a call to `+1 425 XXX XX XX` or `+1 206 XXX XX XX`, the call is first routed to SBC `sbc1.contoso.biz` or `sbc2.contoso.biz`. If both sbc1 nor sbc2 are unavailable, the route with lower priority is tried (`sbc3.contoso.biz` and `sbc4.contoso.biz`). If none of the SBCs of a second route are available, the third route is tried. If sbc5 is also not available, the call is dropped. Also, if a user dials `+1 321 XXX XX XX`, the call goes to `sbc5.contoso.biz`, and it isn't available, the call is dropped.
 
 > [!NOTE]
 > Failover to the next SBC in voice routing works only for response codes 408, 503, and 504.
diff --git a/articles/machine-learning/v1/how-to-setup-authentication.md b/articles/machine-learning/v1/how-to-setup-authentication.md
@@ -55,6 +55,8 @@ To use a service principal (SP), you must first create the SP. Then grant it acc
 > When using a service principal, grant it the __minimum access required for the task__ it is used for. For example, you would not grant a service principal owner or contributor access if all it is used for is reading the access token for a web deployment.
 >
 > The reason for granting the least access is that a service principal uses a password to authenticate, and the password may be stored as part of an automation script. If the password is leaked, having the minimum access required for a specific tasks minimizes the malicious use of the SP.
+> 
+> You should rotate secrets such as the service principal password on a regular basis.
 
 The easiest way to create an SP and grant access to your workspace is by using the [Azure CLI](/cli/azure/install-azure-cli). To create a service principal and grant it access to your workspace, use the following steps:
 
diff --git a/articles/storage/files/authorize-data-operations-portal.md b/articles/storage/files/authorize-data-operations-portal.md
@@ -4,7 +4,7 @@ description: When you access file data using the Azure portal, the portal makes
 author: khdownie
 ms.service: azure-file-storage
 ms.topic: how-to
-ms.date: 11/15/2023
+ms.date: 08/19/2024
 ms.author: kendownie
 ---
 
@@ -61,7 +61,8 @@ When you attempt to access file data in the Azure portal, the portal first check
 
 You can change the authentication method for individual file shares. By default, the portal uses the current authentication method. To determine the current authentication method, follow these steps.
 
-1. Navigate to your storage account in the Azure portal and select **Data storage** > **File shares** from the left navigation.
+1. Navigate to your storage account in the Azure portal.
+1. In the service menu, under **Data storage**, select **File shares**.
 1. Select a file share.
 1. Select **Browse**.
 1. The **Authentication method** indicates whether you're currently using the storage account access key or your Microsoft Entra account to authenticate and authorize file share operations. If you're currently authenticating using the storage account access key, you'll see **Access Key** specified as the authentication method, as in the following image. If you're authenticating using your Microsoft Entra account, you'll see **Microsoft Entra user account** specified instead.
diff --git a/articles/storage/files/understanding-billing.md b/articles/storage/files/understanding-billing.md
diff --git a/articles/vpn-gateway/index.yml b/articles/vpn-gateway/index.yml
