Merge pull request #314226 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: Taojunshen

articles/app-service/manage-backup.md

@@ -120,6 +120,9 @@ There are two types of backups in App Service. If your app is in a supported pri
 1. At the top of the **Backups** page, select **Configure custom backups**.
 
 1. In **Storage account**, select an existing storage account in the same subscription or select **Create new**. Repeat in **Container**.
+    > [!NOTE]
+    > Custom backups for Azure App Service require an Azure Storage account that supports Shared Access Signature (SAS)–based authorization. Managed Identity–based authentication to the storage account isn't supported for App Service backup and restore operations.
+   
 
     To back up the linked databases, select **Next: Advanced** > **Include database**, and select the databases to backup.
 

articles/iot-hub-device-update/configure-access-control-device-update.md

@@ -24,6 +24,7 @@ For users to access Azure Device Update for IoT Hub, you must grant them access
 
 The following roles are available for assigning access to Device Update:
 
+- Device Update Contributor
 - Device Update Administrator
 - Device Update Reader
 - Device Update Content Administrator

articles/iot-hub-device-update/device-update-control-access.md

@@ -21,6 +21,7 @@ Device Update supports the following RBAC roles. For more information, see [Conf
 
 |   Role Name   | Description  |
 | :--------- | :---- |
+|  Device Update Contributor | Can manage all Device Update resources  |
 |  Device Update Administrator | Has access to all Device Update resources  |
 |  Device Update Reader| Can view all updates and deployments |
 |  Device Update Content Administrator | Can view, import, and delete updates  |