Merge pull request #209992 from zackliu/signalrmsi

Update aad in function

Author: 19BMG00

articles/azure-signalr/howto-use-managed-identity.md

@@ -79,23 +79,21 @@ We provide libraries and code samples that show how to handle token validation.
 
 Setting access token validation in Function App is easy and efficient without code works.
 
-1. In the **Authentication (classic)** page, switch **App Service Authentication** to **On**.
+1. In the **Authentication** page, click **Add identity provider**
 
 2. Select **Log in with Azure Active Directory** in **Action to take when request is not authenticated**.
 
-3. In the Authentication Provider, click into **Azure Active Directory**
-
-4. In the new page. Select **Express** and **Create New AD App** and then click **OK**
+3. Select **Microsoft** in the identity provider dropdown. The option to create a new registration is selected by default. You can change the name of the registration. For more details on enabling Azure AD provider, please refer to [Configure your App Service or Azure Functions app to use Azure AD login](../app-service/configure-authentication-provider-aad.md)
     :::image type="content" source="media/signalr-howto-use-managed-identity/function-aad.png" alt-text="Function Aad":::
 
-5. Navigate to SignalR Service and follow [steps](howto-use-managed-identity.md#add-a-system-assigned-identity) to add a system-assigned identity or user-assigned identity.
+4. Navigate to SignalR Service and follow [steps](howto-use-managed-identity.md#add-a-system-assigned-identity) to add a system-assigned identity or user-assigned identity.
 
-6. Get into **Upstream settings** in SignalR Service and choose **Use Managed Identity** and **Select from existing Applications**. Select the application you created previously.
+5. Get into **Upstream settings** in SignalR Service and choose **Use Managed Identity** and **Select from existing Applications**. Select the application you created previously.
 
 After these settings, the Function App will reject requests without an access token in the header.
 
 > [!Important] 
-> To pass the authentication, the *Issuer Url* must match the *iss* claim in token. Currently, we only support v1 endpoint (see [v1.0 and v2.0](../active-directory/develop/access-tokens.md)), so the *Issuer Url* should look like `https://sts.windows.net/<tenant-id>/`. Check the *Issuer Url* configured in Azure Function. For **Authentication**, go to *Identity provider* -> *Edit* -> *Issuer Url* and for **Authentication (classic)**, go to *Azure Active Directory* -> *Advanced* -> *Issuer Url*
+> To pass the authentication, the *Issuer Url* must match the *iss* claim in token. Currently, we only support v1 endpoint (see [v1.0 and v2.0](../active-directory/develop/access-tokens.md)), so the *Issuer Url* should look like `https://sts.windows.net/<tenant-id>/`. Check the *Issuer Url* configured in Azure Function. For **Authentication**, go to *Identity provider* -> *Edit* -> *Issuer Url*
 
 
 ## Use a managed identity for Key Vault reference