Merge pull request #231678 from MicrosoftDocs/main

Publish to Live Wednesday 4AM PST, 03/22

Author: PMEds28

.openpublishing.redirection.json

@@ -22445,6 +22445,11 @@
             "source_path": "articles/private-multi-access-edge-compute-mec/metaswitch-fusion-core-overview.md",
             "redirect_URL": "/azure/private-5g-core",
             "redirect_document_id": false
+        },        
+        {
+            "source_path": "articles/private-5g-core/modify-site-plan.md",
+            "redirect_URL": "/azure/private-5g-core/modify-service-plan",
+            "redirect_document_id": false
         },
         {
             "source_path": "articles/communications-gateway/rotate-secrets.md",
@@ -22455,6 +22460,11 @@
             "source_path": "articles/batch/high-availability-disaster-recovery.md",
             "redirect_URL": "/azure/reliability/reliability-batch",
             "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/communication-services/concepts/bring-your-own-storage.md",
+            "redirect_url": "/azure/communication-services/concepts/call-automation/call-recording/bring-your-own-storage",
+            "redirect_document_id": false
         }
 
     ]

articles/active-directory/authentication/howto-authentication-passwordless-phone.md

@@ -7,13 +7,13 @@ services: active-directory
 ms.service: active-directory
 ms.subservice: authentication
 ms.topic: how-to
-ms.date: 01/29/2023
+ms.date: 03/21/2023
 
 
 ms.author: justinha
 author: justinha
 manager: amycolannino
-ms.reviewer: librown
+ms.reviewer: librown; tilarso
 
 ms.collection: M365-identity-device-management
 ---
@@ -78,7 +78,19 @@ To enable the authentication method for passwordless phone sign-in, complete the
 
 ## User registration 
 
-Users register themselves for the passwordless authentication method of Azure AD. For users who already registered the Microsoft Authenticator app for [multi-factor authentication](./concept-mfa-howitworks.md), skip to the next section, [enable phone sign-in](#enable-phone-sign-in). To register the Microsoft Authenticator app, follow these steps:
+Users register themselves for the passwordless authentication method of Azure AD. For users who already registered the Microsoft Authenticator app for [multi-factor authentication](./concept-mfa-howitworks.md), skip to the next section, [enable phone sign-in](#enable-phone-sign-in). 
+
+### Direct phone Sign-in registration 
+Users can register for passwordless phone sign-in directly within the Microsoft Authenticator app  without the need to first registering Microsoft Authenticator with their account, all while never accruing a password. Here's how:
+1. Acquire a [Temporary Access Pass](../authentication/howto-authentication-temporary-access-pass.md) from your Admin or Organization. 
+2. Download and install the Microsoft Authenticator app on your mobile device. 
+3. Open Microsoft Authenticator and click **Add account** and then choose **Work or school account.**
+4. Choose **Sign in." 
+5. Follow the instructions to sign-in with your account using the Temporary Access Pass provided by your Admin or Organization. 
+6. Once signed-in, continue following the additional steps to set up phone sign-in. 
+
+### Guided registration with My Sign-ins 
+To register the Microsoft Authenticator app, follow these steps:
 
 1. Browse to [https://aka.ms/mysecurityinfo](https://aka.ms/mysecurityinfo).
 1. Sign in, then select **Add method** > **Authenticator app** > **Add** to add Microsoft Authenticator.

articles/active-directory/saas-apps/servicenow-provisioning-tutorial.md

@@ -87,13 +87,7 @@ To configure automatic user provisioning for ServiceNow in Azure AD:
 
 1. Set **Provisioning Mode** to **Automatic**.
 
-1. In the **Admin Credentials** section, enter your ServiceNow tenant URL, Client ID, Client Secret and Authorization Endpoint. Select **Test Connection** to ensure that Azure AD can connect to ServiceNow. [This ServiceNow documentation](https://docs.servicenow.com/bundle/utah-platform-security/page/administer/security/task/t_CreateEndpointforExternalClients.html) outlines how to generate these values.
-   ![Screenshot that shows the Service Provisioning page, where you can enter admin credentials.](./media/servicenow-provisioning-tutorial/servicenow-provisioning.png)
-
-   > [!NOTE]
-   > - Tenant URL: https://**InsertInstanceName**.service-now.com/api/now/scim
-   > - Authorization Endpoint: https://**InsertInstanceName**.service-now.com/oauth_auth.do?response_type=code&client_id=**InsertClientID**&state=1&scope=useraccount&redirect_uri=https%3A%2F%2Fportal.azure.com%2FTokenAuthorize
-   > - Token Endoint: https://**InsertInstanceName**.service-now.com/api/now/scim
+1. In the **Admin Credentials** section, enter your ServiceNow admin credentials and username. Select **Test Connection** to ensure that Azure AD can connect to ServiceNow. If the connection fails, ensure that your ServiceNow account has admin permissions and try again.
 
 1. In the **Notification Email** box, enter the email address of a person or group that should receive the provisioning error notifications. Then select the **Send an email notification when a failure occurs** check box.
 

articles/aks/enable-host-encryption.md

@@ -34,7 +34,7 @@ This feature can only be set at cluster creation or node pool creation time.
 
 ## Use host-based encryption on new clusters
 
-Configure the cluster agent nodes to use host-based encryption when the cluster is created. 
+Configure the cluster agent nodes to use host-based encryption when the cluster is created.
 
 ```azurecli-interactive
 az aks create --name myAKSCluster --resource-group myResourceGroup -s Standard_DS2_v2 -l westus2 --enable-encryption-at-host
@@ -52,12 +52,13 @@ az aks nodepool add --name hostencrypt --cluster-name myAKSCluster --resource-gr
 
 If you want to create new node pools without the host-based encryption feature, you can do so by omitting the `--enable-encryption-at-host` parameter.
 
-## Next steps
-
-Review [best practices for AKS cluster security][best-practices-security]
-Read more about [host-based encryption](../virtual-machines/disk-encryption.md#encryption-at-host---end-to-end-encryption-for-your-vm-data).
+> [!NOTE]
+> After you enable host-based encryption on your cluster, make sure you provide the proper access to your Azure Key Vault to enable encryption at rest. For more information, see [Control access][control-keys] and [Azure built-in roles for Key Vault data plane operations][akv-built-in-roles].
 
+## Next steps
 
+- Review [best practices for AKS cluster security][best-practices-security].
+- Read more about [host-based encryption](../virtual-machines/disk-encryption.md#encryption-at-host---end-to-end-encryption-for-your-vm-data).
 <!-- LINKS - external -->
 
 <!-- LINKS - internal -->
@@ -70,3 +71,5 @@ Read more about [host-based encryption](../virtual-machines/disk-encryption.md#e
 [az-feature-register]: /cli/azure/feature#az_feature_register
 [az-feature-list]: /cli/azure/feature#az_feature_list
 [az-provider-register]: /cli/azure/provider#az_provider_register
+[control-keys]: ../key-vault/general/best-practices.md#control-access-to-your-vault
+[akv-built-in-roles]: ../key-vault/general/rbac-guide.md#azure-built-in-roles-for-key-vault-data-plane-operations

articles/app-service/tutorial-python-postgresql-app.md

@@ -509,7 +509,7 @@ Follow the steps below to setup the Azure Developer CLI and provision and deploy
     powershell -ex AllSigned -c "Invoke-RestMethod 'https://aka.ms/install-azd.ps1' | Invoke-Expression"
     ```
 
-    ### [Linux/MacOS](#tab/linuxmac)
+    ### [macOS/Linux](#tab/mac-linux)
 
     ```azdeveloper
     curl -fsSL https://aka.ms/install-azd.sh | bash 

articles/azure-cache-for-redis/cache-how-to-premium-persistence.md

@@ -6,7 +6,7 @@ author: flang-msft
 ms.author: franlanglois
 ms.service: cache
 ms.topic: conceptual
-ms.date: 01/23/2023
+ms.date: 03/23/2023
 
 ---
 # Configure data persistence for a Premium Azure Cache for Redis instance
@@ -117,6 +117,7 @@ The following list contains answers to commonly asked questions about Azure Cach
 - [Will I be charged for the storage being used in Data Persistence](#will-i-be-charged-for-the-storage-being-used-in-data-persistence)
 - [How frequently does RDB and AOF persistence write to my blobs, and should I enable soft delete?](#how-frequently-does-rdb-and-aof-persistence-write-to-my-blobs-and-should-i-enable-soft-delete)
 - [Will having firewall exceptions on the storage account affect persistence](#will-having-firewall-exceptions-on-the-storage-account-affect-persistence)
+- [How do I check if soft delete is enabled on my storage account?](#how-do-i-check-if-soft-delete-is-enabled-on-my-storage-account)
 
 ### RDB persistence
 

articles/azure-functions/storage-considerations.md

@@ -2,7 +2,7 @@
 title: Storage considerations for Azure Functions
 description: Learn about the storage requirements of Azure Functions and about encrypting stored data. 
 ms.topic: conceptual
-ms.date: 12/13/2022
+ms.date: 03/21/2023
 ---
 
 # Storage considerations for Azure Functions
@@ -27,6 +27,8 @@ To learn more about storage account types, see [Storage account overview](../sto
 
 While you can use an existing storage account with your function app, you must make sure that it meets these requirements. Storage accounts created as part of the function app create flow in the Azure portal are guaranteed to meet these storage account requirements. In the portal, unsupported accounts are filtered out when choosing an existing storage account while creating a function app. In this flow, you're only allowed to choose existing storage accounts in the same region as the function app you're creating. To learn more, see [Storage account location](#storage-account-location).
 
+Storage accounts secured by using firewalls or virtual private networks also can't be used in the portal creation flow. For more information, see [Restrict your storage account to a virtual network](functions-networking-options.md#restrict-your-storage-account-to-a-virtual-network).
+
 <!-- JH: Does using a Premium Storage account improve perf? -->
 
 ## Storage account guidance