Merge pull request #213162 from MicrosoftDocs/main

Publish to live, Friday 4AM PST 9/30

Author: Maggiemouse1

.openpublishing.redirection.json

@@ -6308,6 +6308,21 @@
             "redirect_url": "/azure/storage/blobs/storage-auth-abac",
             "redirect_document_id": false
         },
+        {
+            "source_path": "articles/storage/blobs/reference.md",
+            "redirect_url": "/azure/storage/blobs/storage-blobs-introduction",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "articles/storage/queues/reference.md",
+            "redirect_url": "/azure/storage/queues/storage-queues-introduction",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "articles/storage/files/reference.md",
+            "redirect_url": "/azure/storage/files/storage-files-introduction",
+            "redirect_document_id": false
+        },
         {
             "source_path_from_root": "/articles/storage/storage-client-side-encryption.md",
             "redirect_url": "/azure/storage/common/storage-client-side-encryption",
@@ -21271,12 +21286,12 @@
         {
             "source_path_from_root": "/articles/storage/vs-storage-cloud-services-getting-started-queues.md",
             "redirect_url": "/azure/visual-studio/vs-storage-cloud-services-getting-started-queues",
-            "redirect_document_id": true
+            "redirect_document_id": false
         },
         {
             "source_path_from_root": "/articles/storage/vs-storage-cloud-services-getting-started-tables.md",
             "redirect_url": "/azure/visual-studio/vs-storage-cloud-services-getting-started-tables",
-            "redirect_document_id": true
+            "redirect_document_id": false
         },
         {
             "source_path_from_root": "/articles/storage/vs-storage-cloud-services-what-happened.md",

articles/active-directory/app-provisioning/customize-application-attributes.md

@@ -204,7 +204,7 @@ Use the steps below to provision roles for a user to your application. Note that
   ![Add SingleAppRoleAssignment](./media/customize-application-attributes/edit-attribute-singleapproleassignment.png)
   - **Things to consider**
     - Ensure that multiple roles are not assigned to a user. We cannot guarantee which role will be provisioned.
-    
+    - SingleAppRoleAssignments is not compatible with setting scope to "Sync All users and groups." 
   - **Example request (POST)** 
 
    ```json

articles/active-directory/manage-apps/toc.yml

@@ -212,9 +212,9 @@
         href: silverfort-azure-ad-integration.md
     - name: Single sign-on
       items:
-      - name: Enable single sign-on with SAML
-        href: add-application-portal-setup-oidc-sso.md
-      - name: Enable Linked based single sign-on
+      - name: Enable Single sign-on with SAML
+        href: add-application-portal-setup-sso.md
+      - name: Enable Linked single sign-on
         href: configure-linked-sign-on.md
       - name: Enable OpenID Connect based single sign-on
         href: add-application-portal-setup-oidc-sso.md

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

@@ -9,7 +9,7 @@ ms.service: active-directory
 ms.subservice: saas-app-tutorial
 ms.workload: identity
 ms.topic: tutorial
-ms.date: 07/21/2022
+ms.date: 09/29/2022
 ms.author: jeedes
 
 ---
@@ -82,16 +82,10 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
     b. In the **Reply URL** textbox, type a URL using the following pattern:
     `https://<CustomerDomain>.identity.lusid.com/sso/saml2/<ID>`
 
-1. Click **Set additional URLs** and perform the following steps, if you wish to configure the application in **SP** initiated mode: 
-
-    a. In the **Sign-on URL** text box, type a URL using the following pattern:
-    `https://<CustomerDomain>.lusid.com/ `
-
-    b. In the **Relay State** text box, type a URL using the following pattern:
-    `https://<CustomerDomain>.lusid.com/app/home`
+1. If you wish to configure the application in **SP** initiated mode, click **Set additional URLs** and type a URL in the **Relay State** text box using the following pattern: `https://<CustomerDomain>.lusid.com/app/home`
 
     > [!Note]
-    > These values are not real. Update these values with the actual Identifier, Reply URL, Sign on URL and Relay State URL. Contact [LUSID support team](mailto:[email protected]) to get these values. 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, Reply URL, and Relay State URL. Contact [LUSID support team](mailto:[email protected]) to get these values. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
 
 1. LUSID application expects the SAML assertions in a specific format, which requires you to add custom attribute mappings to your SAML token attributes configuration. The following screenshot shows the list of default attributes.
 

articles/active-directory/saas-apps/media/confluencemicrosoft-tutorial/confluence-configure-addon.png

@@ -9,7 +9,7 @@ ms.service: active-directory
 ms.subservice: saas-app-tutorial
 ms.workload: identity
 ms.topic: tutorial
-ms.date: 09/06/2022
+ms.date: 09/27/2022
 ms.author: jeedes
 
 ---
@@ -81,15 +81,18 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
     a. In the **Reply URL** textbox, type the URL: 
     `https://zola-prod.auth.eu-west-3.amazoncognito.com/saml2/idpresponse`
 
-    b. In the **Sign-on URL** textbox, type the URL:
-    `https://app.zola.fr`
+    b. In the **Sign-on URL** textbox, type the URL provided by Zola:
+    `https://app.zola.fr?company=<MYCOMPANYID>`
 
     c. In the **Relay State** textbox, type the URL:
-    `https://app.zola.fr/version-test/dashboard-v2`
+    `https://app.zola.fr/dashboard-v2`
 
-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.
+    > [!NOTE]
+	> The Sign-on URL value is not real. Update the value with the actual Sign on URL. Contact [Zola support team](mailto:[email protected]) to get the value. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
 
-    ![Screenshot shows the Certificate download link.](common/certificatebase64.png "Certificate")
+1. On the **Set up single sign-on with SAML** page, in the **SAML Signing Certificate** section,  find **Federation Metadata XML** and select **Download** to download the certificate and save it on your computer.
+
+    ![Screenshot shows the Certificate download link.](common/metadataxml.png "Certificate")
 
 1. On the **Set up Zola** section, copy the appropriate URL(s) based on your requirement.
 
@@ -131,11 +134,11 @@ In this section, you create a user called Britta Simon at Zola. Work with [Zola
 
 In this section, you test your Azure AD single sign-on configuration with following options. 
 
-* Click on **Test this application** in Azure portal. This will redirect to Zola Sign-on URL where you can initiate the login flow. 
+* Click on **Test this application** in Azure portal. This will redirect to Zola Sign on URL where you can initiate the login flow. 
 
-* Go to Zola Sign-on URL directly and initiate the login flow from there.
+* Go to Zola Sign on URL directly and initiate the login flow from there.
 
-* You can use Microsoft My Apps. When you click the Zola tile in the My Apps, this will redirect to Zola Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md).
+* You can use Microsoft My Apps. When you click the Zola tile in the My Apps, this will redirect to Zola Sign on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md).
 
 ## Next steps
 

articles/active-directory/saas-apps/media/jiramicrosoft-tutorial/jira-configure-addon.png

@@ -7,7 +7,7 @@ author: flang-msft
 ms.author: franlanglois
 ms.service: cache
 ms.topic: conceptual
-ms.date: 09/29/2022
+ms.date: 09/30/2022
 
 ---
 
@@ -23,11 +23,9 @@ On June 30, 2023, we'll retire version 4 for Azure Cache for Redis instances. Be
 We recommend that you upgrade your caches on your own to accommodate your schedule and the needs of your users to make the upgrade as convenient as possible.
 
 The open-source Redis version 4 was released several years ago and is now retired. Version 4 no longer receives critical bug or security fixes from the community. Azure Cache for Redis offers open-source Redis as a managed service on Azure. To stay in sync with the open-source offering, we'll also retire version 4.
-<!-- Can we be more specific about when open-source Redis 4 was retired -->
-
 Microsoft continues to backport security fixes from recent versions to version 4 until retirement. We encourage you to upgrade your cache to version 6 sooner, so you can use the rich feature set that Redis version 6 has to offer. For more information, See the Redis 6 GA announcement for more details.
 
-To upgrade your version 4 Azure Cache for Redis instance, see our [Upgrade an existing Redis 4 cache to Redis 6](cache-how-to-version.md#upgrade-an-existing-redis-4-cache-to-redis-6. If your cache instances have geo-replication enabled, you’re required to unlink the caches before upgrade.
+To upgrade your version 4 Azure Cache for Redis instance, see [How to upgrade an existing Redis 4 cache to Redis 6](cache-how-to-upgrade.md). If your cache instances have geo-replication enabled, you’re required to unlink the caches before upgrade.
 
 ### Important upgrade timelines
 

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

@@ -9,7 +9,7 @@ ms.reviewer: vitalyg
 
 # Resource Manager template samples for creating Application Insights resources
 
-This article includes sample [Azure Resource Manager templates](../../azure-resource-manager/templates/syntax.md) to deploy and configure [classic Application Insights resources](../app/create-new-resource.md) and the new [preview workspace-based Application Insights resources](../app/create-workspace-resource.md). Each sample includes a template file and a parameters file with sample values to provide to the template.
+This article includes sample [Azure Resource Manager templates](../../azure-resource-manager/templates/syntax.md) to deploy and configure [classic Application Insights resources](../app/create-new-resource.md) and the new [workspace-based Application Insights resources](../app/create-workspace-resource.md). Each sample includes a template file and a parameters file with sample values to provide to the template.
 
 [!INCLUDE [azure-monitor-samples](../../../includes/azure-monitor-resource-manager-samples.md)]
 
@@ -136,7 +136,7 @@ resource component 'Microsoft.Insights/components@2020-02-02' = {
 
 ## Workspace-based Application Insights resource
 
-The following sample creates a [workspace-based Application Insights resource](../app/create-workspace-resource.md). Workspace-based Application Insights are currently in **preview**.
+The following sample creates a [workspace-based Application Insights resource](../app/create-workspace-resource.md). 
 
 ### Template file
 

articles/azure-cache-for-redis/cache-retired-features.md

@@ -12,7 +12,7 @@ ms.service: azure-netapp-files
 ms.workload: storage
 ms.tgt_pltfrm: na
 ms.topic: conceptual
-ms.date: 09/28/2022
+ms.date: 09/29/2022
 ms.author: ramakk
 ---
 # Guidelines for Azure NetApp Files network planning
@@ -87,7 +87,9 @@ The following table describes what’s supported for each network features confi
 |     Dual stack (IPv4 and   IPv6) VNet    |     No <br> (IPv4 only supported)    |     No <br> (IPv4 only supported)    |
 
 > [!IMPORTANT]
-> Conversion between Basic and Standard networking features in either direction is not currently supported. Additionally, you cannot create a Standard volume from the snapshot of a Basic volume.
+> Conversion between Basic and Standard networking features in either direction is not currently supported. 
+>
+> Additionally, you can create Basic volumes from Basic volume snapshots and Standard volumes from Standard volume snapshots. Creating a Basic volume from a Standard volume snapshot is not supported. Creating a Standard volume from a Basic volume snapshot is not supported.
 
 ### Supported network topologies