Merge pull request #237949 from MicrosoftDocs/main

Publish to live, Friday 4 AM PST, 5/12

Author: ttorble

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

@@ -1,5 +1,5 @@
 ---
-title: 'Tutorial: Azure Active Directory single sign-on (SSO) integration with Hootsuite'
+title: 'Tutorial: Azure Active Directory SSO integration with Hootsuite'
 description: Learn how to configure single sign-on between Azure Active Directory and Hootsuite.
 services: active-directory
 author: jeevansd
@@ -9,13 +9,13 @@ ms.service: active-directory
 ms.subservice: saas-app-tutorial
 ms.workload: identity
 ms.topic: tutorial
-ms.date: 11/21/2022
+ms.date: 05/10/2023
 ms.author: jeedes
 ---
 
 # Tutorial: Azure Active Directory single sign-on (SSO) integration with Hootsuite
 
-In this tutorial, you'll learn how to integrate Hootsuite with Azure Active Directory (Azure AD). When you integrate Hootsuite with Azure AD, you can:
+In this tutorial, you learn how to integrate Hootsuite with Azure Active Directory (Azure AD). When you integrate Hootsuite with Azure AD, you can:
 
 * Control in Azure AD who has access to Hootsuite.
 * Enable your users to be automatically signed-in to Hootsuite with their Azure AD accounts.
@@ -74,24 +74,13 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
 
    ![Edit Basic SAML Configuration](common/edit-urls.png)
 
-1. On the **Basic SAML Configuration** section, if you wish to configure the application in **IDP** initiated mode, perform the following step:
+1. On the **Basic SAML Configuration** section, the user does not have to perform any step as the app is already pre-integrated with Azure.
 
-    In the **Reply URL** text box, type a URL using one of the following patterns:
-
-    | Reply URL |
-    |---|
-    |`https://hootsuite.com/member/sso-complete`|
-    |`https://hootsuite.com/sso/<ORG_ID>`|
-    |
-
-1. Click **Set additional URLs** and perform the following step if you wish to configure the application in **SP** initiated mode:
+1. Perform the following step, if you wish to configure the application in **SP** initiated mode:
 
     In the **Sign-on URL** text box, type the URL:
     `https://hootsuite.com/login`
 
-	> [!NOTE]
-	> These values are not real. Update these values with the actual Reply URL. Contact [Hootsuite Client support team](https://hootsuite.com/about/contact-us#) to get these values. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
-
 1. On the **Set up single sign-on with SAML** page, in the **SAML Signing Certificate** section,  find **Certificate (Base64)** and select **Download** to download the certificate and save it on your computer.
 
 	![The Certificate download link](common/certificatebase64.png)
@@ -102,7 +91,7 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
 
 ### Create an Azure AD test user
 
-In this section, you'll create a test user in the Azure portal called B.Simon.
+In this section, you create a test user in the Azure portal called B.Simon.
 
 1. From the left pane in the Azure portal, select **Azure Active Directory**, select **Users**, and then select **All users**.
 1. Select **New user** at the top of the screen.
@@ -114,7 +103,7 @@ In this section, you'll create a test user in the Azure portal called B.Simon.
 
 ### Assign the Azure AD test user
 
-In this section, you'll enable B.Simon to use Azure single sign-on by granting access to Hootsuite.
+In this section, you enable B.Simon to use Azure single sign-on by granting access to Hootsuite.
 
 1. In the Azure portal, select **Enterprise Applications**, and then select **All applications**.
 1. In the applications list, select **Hootsuite**.

articles/application-gateway/configuration-frontend-ip.md

@@ -35,11 +35,11 @@ Only one public IP address and one private IP address is supported. You choose t
 A frontend IP address is associated to a *listener*, which checks for incoming requests on the frontend IP.
 
 >[!NOTE] 
-> You can create private and public listeners with the same port number (Preview feature). However, be aware of any Network Security Group (NSG) associated with the application gateway subnet. Depending on your NSG's configuration, you may need an inbound rule with **Destination IP addresses** as your application gateway's public and private frontend IPs.
+> You can create private and public listeners with the same port number (Preview feature). However, be aware of any Network Security Group (NSG) associated with the application gateway subnet. Depending on your NSG's configuration, you may need an inbound rule with **Destination IP addresses** as your application gateway subnet's IP prefix.
 > 
 > **Inbound Rule**:
 > - Source: (as per your requirement)
-> - Destination IP addresses: Public and Private frontend IPs of your application gateway.
+> - Destination IP addresses: IP prefix of your application gateway subnet.
 > - Destination Port: (as per listener configuration)
 > - Protocol: TCP
 > 

articles/azure-monitor/app/live-stream.md

@@ -433,14 +433,13 @@ As described in the [Azure TLS 1.2 migration announcement](https://azure.microso
 
 ### "Data is temporarily inaccessible" status message
 
-When navigating to Live Metrics, you may see a banner with the status message: "Data is temporarily inaccessible. The updates on our status are posted here https://aka.ms/aistatus" 
+When navigating to Live Metrics, you may see a banner with the status message: "Data is temporarily inaccessible. The updates on our status are posted here https://aka.ms/aistatus"
 
-Verify if any firewalls or browser extensions are blocking access to Live Metrics. For example, some popular ad-blocker extensions block connections to \*.monitor.azure.com. In order to use the full capabilities of Live Metrics, either disable the ad-blocker extension or add an exclusion rule for the domain \*.livediagnostics.monitor.azure.com to your ad-blocker, firewall, etc. 
+Follow the link to the *Azure status* page and check if there's an activate outage affecting Application Insights. If there's no outage, verify if any firewalls or browser extensions are blocking access to Live Metrics. For example, some popular ad-blocker extensions block connections to `*.monitor.azure.com`. In order to use the full capabilities of Live Metrics, either disable the ad-blocker extension or add an exclusion rule for the domain `*.livediagnostics.monitor.azure.com` to your ad-blocker, firewall, etc.
 
 ### Unexpected large number of requests to livediagnostics.monitor.azure.com
 
-Heavier traffic is expected while the LiveMetrics pane is open. Navigate away from the LiveMetrics pane to restore normal traffic flow of traffic.
-Application Insights SDKs poll QuickPulse endpoints with REST API calls once every five seconds to check if the LiveMetrics pane is being viewed.
+Heavier traffic is expected while the LiveMetrics pane is open. Navigate away from the LiveMetrics pane to restore normal traffic flow of traffic. Application Insights SDKs poll QuickPulse endpoints with REST API calls once every five seconds to check if the LiveMetrics pane is being viewed.
 
 The SDKs will send new metrics to QuickPulse every one second while the LiveMetrics pane is open.
 

articles/azure-resource-manager/management/move-support-resources.md

@@ -456,7 +456,7 @@ Before starting your move operation, review the [checklist](./move-resource-grou
 
 
 > [!IMPORTANT]
-> See [Cloud Services (extended support) deployment move guidance](./move-limitations/classic-model-move-limitations.md). Cloud Services (extended support) deployment resources can be moved across subscriptions with an operation specific to that scenario.
+> See [Cloud Services (extended support) deployment move guidance](./move-limitations/cloud-services-extended-support.md). Cloud Services (extended support) deployment resources can be moved across subscriptions with an operation specific to that scenario.
 
 > [!div class="mx-tableFixed"]
 > | Resource type | Resource group | Subscription | Region move |

articles/azure-video-indexer/release-notes.md

@@ -18,6 +18,12 @@ To stay up-to-date with the most recent Azure Video Indexer developments, this a
 * Bug fixes
 * Deprecated functionality
 
+## May 2023
+
+### Topics insight improvements 
+
+We now support all five levels of IPTC ontology. 
+
 ## April 2023
 
 ### Resource Health support

articles/cloud-services-extended-support/faq.yml

@@ -4,8 +4,8 @@ metadata:
   description: Frequently asked questions for Azure Cloud Services (extended support)
   ms.topic: faq
   ms.service: cloud-services-extended-support
-  author: gachandw
-  ms.author: gachandw
+  author: hirshah
+  ms.author: hirshah
   ms.reviewer: mimckitt
   ms.date: 10/13/2020
   ms.custom: references_regions
@@ -134,6 +134,11 @@ sections:
           Does Cloud Services (extended support) allow CTP package format?
         answer: |
           CTP package format is not supported in Cloud Services (extended support). However, it allows an enhanced package size limit of 800 MB
+                    
+      - question: |
+          CSES requires its package files to be stored in a storage account. Can the storage account be set as "enable access from selected virtual networks"
+        answer: |
+          CSES does not support Managed Identity Support. So, Storage account by design does not allow CSES to access the package files when storage account is enabled only selected VNet in the setting.
 
   - name: Migration
     questions: