Merge pull request #239365 from MicrosoftDocs/main

5/25 PM Publish

Author: huypub

README.md

@@ -1,6 +1,6 @@
 # Microsoft Azure Documentation
 
-Welcome to the open-source [documentation](/azure) of [Microsoft Azure](https://azure.microsoft.com). Please review this README file to understand how you can assist in contributing to the Microsoft Azure documentation.
+Welcome to the open-source [documentation](/azure) of [Microsoft Azure](https://azure.microsoft.com). Please review this README file to understand how you can assist in contributing to the Microsoft Azure documentation. 
 
 ## Getting Started
 

articles/active-directory/develop/msal-android-shared-devices.md

@@ -95,13 +95,10 @@ These Microsoft applications support Azure AD's shared device mode:
 
 - [Microsoft Teams](/microsoftteams/platform/)
 - [Microsoft Managed Home Screen](/mem/intune/apps/app-configuration-managed-home-screen-app) app for Android Enterprise
-- [Microsoft Edge](/microsoft-edge) (in Public Preview)
-- [Outlook](/mem/intune/apps/app-configuration-policies-outlook) (in Public Preview)
-- [Microsoft Power Apps](/power-apps) (in Public Preview)
-- [Yammer](/yammer) (in Public Preview)
-
-> [!IMPORTANT]
-> Public preview is provided without a service-level agreement and isn't recommended for production workloads. Some features might be unsupported or have constrained capabilities. For more information, see [Supplemental terms of use for Microsoft Azure previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
+- [Microsoft Edge](/microsoft-edge)
+- [Outlook](/mem/intune/apps/app-configuration-policies-outlook)
+- [Microsoft Power Apps](/power-apps)
+- [Microsoft Viva Engage](/viva/engage/overview) (previously [Yammer](/yammer))
 
 ## Shared device sign-out and the overall app lifecycle
 

articles/active-directory/external-identities/customers/how-to-facebook-federation-customers.md

@@ -8,7 +8,7 @@ ms.service: active-directory
 ms.workload: identity
 ms.subservice: ciam
 ms.topic: how-to
-ms.date: 04/28/2023
+ms.date: 05/24/2023
 ms.author: mimart
 ms.custom: it-pro
 
@@ -38,17 +38,21 @@ If you don't already have a Facebook account, sign up at [https://www.facebook.c
     1. Enter a URL for the **Terms of Service URL**, for example `https://www.contoso.com/tos`. The policy URL is a page you maintain to provide terms and conditions for your application.
     1. Enter a URL for the **User Data Deletion**, for example `https://www.contoso.com/delete_my_data`. The User Data Deletion URL is a page you maintain to provide away for users to request that their data be deleted.
     1. Choose a **Category**, for example `Business and Pages`. Facebook requires this value, but it's not used for Azure AD.
-2. At the bottom of the page, select **Add Platform**, and then select **Website**.
-3. In **Site URL**, enter the address of your website, for example `https://contoso.com`. 
-4. Select **Save Changes**.
-5. From the menu, select the **plus** sign or **Add Product** link next to **PRODUCTS**. Under the **Add Products to Your App**, select **Set up** under **Facebook Login**.
-6. From the menu, select **Facebook Login**, select **Settings**.
-7. In **Valid OAuth redirect URIs**, enter:
-    - `https://login.microsoftonline.com`
-    -  `https://login.microsoftonline.com/te/<tenant ID>/oauth2/authresp`. Replace the tenant ID with your Azure AD for customers tenant ID. To find your tenant ID, go to the [Microsoft Entra admin center](https://entra.microsoft.com). Under **Azure Active Directory**, select **Overview**. Then select the **Overview** tab and copy the **Tenant ID**.
-    - `https://login.microsoftonline.com/te/<tenant name>.onmicrosoft.com/oauth2/authresp`. Replace the tenant name with your Azure AD for customers tenant name.
-8. Select **Save Changes** at the bottom of the page.
-9. To make your Facebook application available to Azure AD, select the Status selector at the top right of the page and turn it **On** to make the Application public, and then select **Switch Mode**. At this point, the Status should change from **Development** to **Live**. For more information, see [Facebook App Development](https://developers.facebook.com/docs/development/release).
+1. At the bottom of the page, select **Add Platform**, and then select **Website**.
+1. In **Site URL**, enter the address of your website, for example `https://contoso.com`. 
+1. Select **Save Changes**.
+1. From the menu, select the **plus** sign or **Add Product** link next to **PRODUCTS**. Under the **Add Products to Your App**, select **Set up** under **Facebook Login**.
+1. From the menu, select **Facebook Login**, select **Settings**.
+1. In **Valid OAuth redirect URIs**, enter the following URIs, replacing `<tenant-ID>` with your customer tenant ID and `<tenant-name>` with your customer tenant name:
+   - `https://login.microsoftonline.com/te/<tenant-ID>/oauth2/authresp`
+   - `https://<tenant-ID>.ciamlogin.com/<tenant-ID>/federation/oidc/www.facebook.com`
+    - `https://<tenant-ID>.ciamlogin.com/<tenant-name>.onmicrosoft.com/federation/oidc/www.facebook.com`
+    - `https://<tenant-ID>.ciamlogin.com/<tenant-ID>/federation/oauth2`
+    - `https://<tenant-ID>.ciamlogin.com/<tenant-name>.onmicrosoft.com/federation/oauth2`
+   > [!NOTE]
+   > To find your customer tenant ID, go to the [Microsoft Entra admin center](https://entra.microsoft.com). Under **Azure Active Directory**, select **Overview**. Then select the **Overview** tab and copy the **Tenant ID**.
+1. Select **Save Changes** at the bottom of the page.
+1. To make your Facebook application available to Azure AD, select the Status selector at the top right of the page and turn it **On** to make the Application public, and then select **Switch Mode**. At this point, the Status should change from **Development** to **Live**. For more information, see [Facebook App Development](https://developers.facebook.com/docs/development/release).
 
 ## Configure Facebook federation in Azure AD for customers
 

articles/active-directory/external-identities/customers/how-to-google-federation-customers.md

@@ -8,7 +8,7 @@ ms.service: active-directory
 ms.workload: identity
 ms.subservice: ciam
 ms.topic: how-to
-ms.date: 04/28/2023
+ms.date: 05/24/2023
 ms.author: mimart
 ms.custom: it-pro
 
@@ -31,21 +31,27 @@ To enable sign-in for customers with a Google account, you need to create an app
 1. Under the **Quick access**, or in the left menu, select **APIs & services** and then **OAuth consent screen**.
 1. For the **User Type**, select **External** and then select **Create**.
 1. On the **OAuth consent screen**, under **App information**
-    1. Enter a **Name** for your application.
-    2. Select a **User support email** address.
-1. Under the **Authorized domains** section, select **Add domain**, and then type *microsoftonline.com*.
+   1. Enter a **Name** for your application.
+   1. Select a **User support email** address.
+1. Under the **Authorized domains** section, select **Add domain**, and then add `ciamlogin.com` and `microsoftonline.com`.
 1. In the **Developer contact information** section, enter comma separated emails for Google to notify you about any changes to your project.
 1. Select **Save and Continue**.
 1. From the left menu, select **Credentials**
 1. Select **Create credentials**, and then **OAuth client ID**.
 1. Under **Application type**, select **Web application**.
-    1. Enter a suitable **Name** for your application, such as "Azure AD for customers."
-    1. For the **Authorized redirect URIs**, enter:
-        - `https://login.microsoftonline.com`
-        -  `https://login.microsoftonline.com/te/<tenant ID>/oauth2/authresp`. Replace the tenant ID with your Azure AD for customers tenant ID. To find your tenant ID, go to the [Microsoft Entra admin center](https://entra.microsoft.com). Under **Azure Active Directory**, select **Overview**. Then select the **Overview** tab and copy the **Tenant ID**.
-        - `https://login.microsoftonline.com/te/<tenant name>.onmicrosoft.com/oauth2/authresp`. Replace the tenant name with your Azure AD for customers tenant name.
-1. Select **Create**.
-1. Copy the values of **Client ID** and **Client secret**. You need both values to configure Google as an identity provider in your tenant. **Client secret** is an important security credential.
+   1. Enter a suitable **Name** for your application, such as "Azure AD for customers."
+   1. In **Valid OAuth redirect URIs**, enter the following URIs, replacing `<tenant-ID>` with your customer tenant ID and `<tenant-name>` with your customer tenant name:
+    - `https://login.microsoftonline.com`
+    - `https://login.microsoftonline.com/te/<tenant-ID>/oauth2/authresp`
+    - `https://login.microsoftonline.com/te/<tenant-name>.onmicrosoft.com/oauth2/authresp`
+    - `https://<tenant-ID>.ciamlogin.com/<tenant-ID>/federation/oidc/accounts.google.com`
+    - `https://<tenant-ID>.ciamlogin.com/<tenant-name>.onmicrosoft.com/federation/oidc/accounts.google.com`
+    - `https://<tenant-ID>.ciamlogin.com/<tenant-ID>/federation/oauth2`
+    - `https://<tenant-ID>.ciamlogin.com/<tenant-name>.onmicrosoft.com/federation/oauth2`
+   > [!NOTE]
+   > To find your customer tenant ID, go to the [Microsoft Entra admin center](https://entra.microsoft.com). Under **Azure Active Directory**, select **Overview**. Then select the **Overview** tab and copy the **Tenant ID**.
+2. Select **Create**.
+3. Copy the values of **Client ID** and **Client secret**. You need both values to configure Google as an identity provider in your tenant. **Client secret** is an important security credential.
 
 > [!NOTE]
 > In some cases, your app might require verification by Google (for example, if you update the application logo). For more information, check out the [Google's verification status guid](https://support.google.com/cloud/answer/10311615#verification-status).

articles/active-directory/saas-apps/parallels-desktop-tutorial.md

@@ -9,7 +9,7 @@ ms.service: active-directory
 ms.subservice: saas-app-tutorial
 ms.workload: identity
 ms.topic: how-to
-ms.date: 02/23/2023
+ms.date: 05/25/2023
 ms.author: jeedes
 
 ---
@@ -66,7 +66,7 @@ Complete the following steps to enable Azure AD single sign-on in the Azure port
     `https://account.parallels.com/webapp/sso/acs/<ID>`
 
     > [!NOTE]
-    > These values are not real. Update these values with the actual Identifier and Reply URL. Please note the Identifier and Reply URL values are customer specific and should be able to specify it manually by copying it from Parallels My Account to the identity provider Azure. Contact [Parallels Desktop Client support team](mailto:parallels.desktop.sso@alludo.com) for any help. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
+    > These values are not real. Update these values with the actual Identifier and Reply URL. Please note the Identifier and Reply URL values are customer specific and should be able to specify it manually by copying it from Parallels My Account to the identity provider Azure. Contact [Parallels Desktop support team](https://www.parallels.com/support/) for any help. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
 
     c. In the **Sign on URL** textbox, type the URL:-
     `https://my.parallels.com/login?sso=1`
@@ -81,11 +81,11 @@ Complete the following steps to enable Azure AD single sign-on in the Azure port
 
 ## Configure Parallels Desktop SSO
 
-To configure single sign-on on **Parallels Desktop** side, you need to send the downloaded **Certificate (PEM)** and appropriate copied URLs from Azure portal to [Parallels Desktop support team](mailto:parallels.desktop.sso@alludo.com). They set this setting to have the SAML SSO connection set properly on both sides.
+To configure single sign-on on **Parallels Desktop** side, you need to send the downloaded **Certificate (PEM)** and appropriate copied URLs from Azure portal to [Parallels Desktop support team](https://www.parallels.com/support/). They set this setting to have the SAML SSO connection set properly on both sides.
 
 ### Create Parallels Desktop test user
 
-In this section, you create a user called Britta Simon at Parallels Desktop. Work with [Parallels Desktop support team](mailto:parallels.desktop.sso@alludo.com) to add the users in the Parallels Desktop platform. Users must be created and activated before you use single sign-on.
+In this section, you create a user called Britta Simon at Parallels Desktop. Work with [Parallels Desktop support team](https://www.parallels.com/support/) to add the users in the Parallels Desktop platform. Users must be created and activated before you use single sign-on.
 
 ## Test SSO 
 

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

@@ -9,7 +9,7 @@ ms.service: active-directory
 ms.subservice: saas-app-tutorial
 ms.workload: identity
 ms.topic: tutorial
-ms.date: 03/29/2023
+ms.date: 05/25/2023
 ms.author: jeedes
 ---
 
@@ -108,7 +108,7 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
 	| Reply URL|
 	|----------|
 	| `https://<instancename>.service-now.com/navpage.do` |
-	| `https://<instancename>.service-now.com/customer.do` |
+	| `https://<instancename>.service-now.com/consumer.do` |
 	|
 
 	d. In **Logout URL**, enter a URL that uses the following pattern:
@@ -177,7 +177,7 @@ In this section, you'll enable B.Simon to use Azure single sign-on by granting a
 	| Sign on URL |
 	|-----------|
 	|  `https://<instance-name>.service-now.com/login_with_sso.do?glide_sso_id=<sys_id of the sso configuration>` |
-	| `https://<instancename>.service-now.com/customer.do` |
+	| `https://<instancename>.service-now.com/consumer.do` |
 	|
 
     b. For **Identifier (Entity ID)**, enter a URL that uses the following pattern:
@@ -188,7 +188,7 @@ In this section, you'll enable B.Simon to use Azure single sign-on by granting a
 	| Reply URL |
 	|-----------|
 	| `https://<instancename>.service-now.com/navpage.do` |
-	| `https://<instancename>.service-now.com/customer.do` |
+	| `https://<instancename>.service-now.com/consumer.do` |
 	|
 
 	d. In **Logout URL**, enter a URL that uses the following pattern:

articles/active-directory/saas-apps/superannotate-tutorial.md

@@ -9,7 +9,7 @@ ms.service: active-directory
 ms.subservice: saas-app-tutorial
 ms.workload: identity
 ms.topic: how-to
-ms.date: 03/13/2023
+ms.date: 05/25/2023
 ms.author: jeedes
 
 ---
@@ -81,13 +81,13 @@ Complete the following steps to enable Azure AD single sign-on in the Azure port
 	| ---------------|  --------- |
     | groups | user.groups [ApplicationGroup] |
 
-1. On the **Set up single sign-on with SAML** page, in the **SAML Signing Certificate** section, click copy button to copy **App Federation Metadata Url** and save it on your computer.
+1. On the **Set up single sign-on with SAML** page, in the **SAML Signing Certificate** section, copy the **App Federation Metadata Url** or download the **Federation Metadata XML** and save it on your computer.
 
     ![Screenshot shows the Certificate download link.](common/copy-metadataurl.png "Certificate")
 
 ## Configure SuperAnnotate SSO
 
-To configure single sign-on on **SuperAnnotate** side, you need to send the **App Federation Metadata Url** to [SuperAnnotate support team](mailto:[email protected]). They set this setting to have the SAML SSO connection set properly on both sides
+To configure single sign-on on **SuperAnnotate** side, you need to set up the copied **App Federation Metadata Url** or the downloaded **Federation Metadata XML** in the SSO setup page of the SuperAnnotate side to have the SAML SSO connection set properly on both sides.
 
 ### Create SuperAnnotate test user
 

articles/advisor/advisor-cost-recommendations.md

@@ -82,6 +82,10 @@ In some cases recommendations can't be adopted or might not be applicable, such
 
 In such cases, simply use the Dismiss/Postpone options associated with the recommendation. 
 
+### Limitations
+- The savings associated with the recommendations are based on retail rates and don't take into account any temporary or long-term discounts that might apply to your account. As a result, the listed savings might be higher than actually possible.  
+- The recommendations don't take into account the presence of Reserved Instances (RI) / Savings plan purchases. As a result, the listed savings might be higher than actually possible. In some cases, for example in the case of cross-series recommendations, depending on the types of SKUs that reserved instances have been purchased for, the costs might increase when the optimization recommendations are followed. We caution you to consider your RI/Savings plan purchases when you act on the right-size recommendations. 
+
 We're constantly working on improving these recommendations. Feel free to share feedback on [Advisor Forum](https://aka.ms/advisorfeedback).
 
 ## Next steps

articles/aks/TOC.yml

@@ -398,10 +398,10 @@
                   href: csi-secrets-store-nginx-tls.md
     - name: Configure private clusters
       items:
-      - name: Create a private cluster
-        href: private-clusters.md
-      - name: Access a private cluster remotely
-        href: command-invoke.md
+        - name: Create a private cluster
+          href: private-clusters.md
+        - name: Access a private cluster remotely
+          href: command-invoke.md
     - name: Configure networking
       items:
         - name: Create or use existing virtual network
@@ -612,6 +612,8 @@
       items:
         - name: About Open Service Mesh
           href: open-service-mesh-about.md
+        - name: Migration Guidance to Istio AKS add-on
+          href: open-service-mesh-istio-migration-guidance.md
         - name: Use the Azure CLI
           href: open-service-mesh-deploy-addon-az-cli.md
         - name: Use Bicep template