Merge pull request #71 from MicrosoftDocs/master

refresh fork

Author: kromerm

.openpublishing.publish.config.json

@@ -817,15 +817,17 @@
   },
   "redirection_files": [
     ".openpublishing.redirection.json",
+    ".openpublishing.redirection.active-directory.json",
     ".openpublishing.redirection.data-factory.json",
     ".openpublishing.redirection.defender-for-iot.json",
     ".openpublishing.redirection.healthcare-apis.json",
+    ".openpublishing.redirection.iot-hub.json",
+    ".openpublishing.redirection.key-vault.json",
     ".openpublishing.redirection.media-services.json",
     ".openpublishing.redirection.security-benchmark.json",
     ".openpublishing.redirection.synapse-analytics.json",
-    ".openpublishing.redirection.key-vault.json",
-    ".openpublishing.redirection.iot-hub.json",
     "articles/azure-relay/.openpublishing.redirection.relay.json",
+    "articles/communication-services/.openpublishing.redirection.communication-services.json",
     "articles/cosmos-db/.openpublishing.redirection.cosmos-db.json",
     "articles/cost-management-billing/.openpublishing.redirection.cost-management-billing.json",
     "articles/data-catalog/.openpublishing.redirection.data-catalog.json",
@@ -835,12 +837,15 @@
     "articles/event-hubs/.openpublishing.redirection.event-hubs.json",
     "articles/hdinsight/.openpublishing.redirection.hdinsight.json",
     "articles/iot-central/.openpublishing.redirection.iot-central.json",
+    "articles/iot-accelerators/.openpublishing.redirection.iot-accelerators.json",
     "articles/iot-develop/.openpublishing.redirection.iot-develop.json",
     "articles/iot-edge/.openpublishing.redirection.iot-edge.json",
     "articles/marketplace/.openpublishing.redirection.marketplace.json",
+    "articles/object-anchors/.openpublishing.redirection.object-anchors.json",
     "articles/purview/.openpublishing.redirection.purview.json",
-    "articles/virtual-machines/.openpublishing.redirection.virtual-machines.json",
     "articles/service-bus-messaging/.openpublishing.redirection.service-bus-messaging.json",
-    "articles/stream-analytics/.openpublishing.redirection.stream-analytics.json"
+    "articles/stream-analytics/.openpublishing.redirection.stream-analytics.json",
+    "articles/virtual-machines/.openpublishing.redirection.virtual-machines.json",
+    "articles/mysql/.openpublishing.redirection.mysql.json"
   ]
 }

.openpublishing.redirection.active-directory.json

@@ -9,6 +9,11 @@
             "source_path_from_root": "/articles/data-factory/turorial-push-lineage-to-purview.md",
             "redirect_url": "/azure/data-factory/tutorial-push-lineage-to-purview",
             "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/data-factory/continuous-integration-deployment.md",
+            "redirect_url": "/azure/data-factory/continuous-integration-delivery",
+            "redirect_document_id": false
         }
     ]
 }

.openpublishing.redirection.data-factory.json

@@ -177,11 +177,6 @@
         "redirect_url": "/azure/healthcare-apis/fhir/register-service-azure-ad-client-app",
         "redirect_document_id": true
     },
-    {
-        "source_path_from_root": "/articles/healthcare-apis/security-controls-policy.md",
-        "redirect_url": "/azure/healthcare-apis/fhir/security-controls-policy",
-        "redirect_document_id": true
-    },
     {
         "source_path_from_root": "/articles/healthcare-apis/tutorial-web-app-fhir-server.md",
         "redirect_url": "/azure/healthcare-apis/fhir/tutorial-web-app-fhir-server",
@@ -334,7 +329,7 @@
     },
     {
         "source_path_from_root": "/articles/healthcare-apis/fhir/partner-ecosystem.md",
-        "redirect_url": "/azure/healthcare-apis/azure-api-for-fhir/partner-ecosystem",
+        "redirect_url": "/azure/healthcare-apis/azure-api-for-fhir/fhir-features-supported",
         "redirect_document_id": true
     },
     {
@@ -456,6 +451,11 @@
         "source_path_from_root": "/articles/healthcare-apis/azure-api-for-fhir/access-fhir-postman-tutorial.md",
         "redirect_url": "/azure/healthcare-apis/use-postman",
         "redirect_document_id": true
-    }
+    },
+    {
+        "source_path_from_root": "/articles/healthcare-apis/fhir/security-controls-policy.md",
+        "redirect_url": "/azure/healthcare-apis/security-controls-policy",
+        "redirect_document_id": true
+    },
   ]
 }

.openpublishing.redirection.healthcare-apis.json

@@ -39,6 +39,27 @@
             "source_path_from_root": "/articles/synapse-analytics/sql-data-warehouse/guidance-for-loading-data.md",
             "redirect_url": "/azure/synapse-analytics/sql/data-loading-best-practices",
             "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/synapse-analytics/cicd/continuous-integration-deployment.md",
+            "redirect_url": "/azure/synapse-analytics/cicd/continuous-integration-delivery",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/synapse-analytics/sql/develop-best-practices.md",
+            "redirect_url": "/azure/synapse-analytics/sql/best-practices-dedicated-sql-pool",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/synapse-analytics/sql-data-warehouse/sql-data-warehouse-best-practices-development.md",
+            "redirect_url": "/azure/synapse-analytics/sql/best-practices-dedicated-sql-pool",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/synapse-analytics/quickstart-sql-on-demand.md",
+            "redirect_url": "/azure/synapse-analytics/quickstart-serverless-sql-pool",
+            "redirect_document_id": false
         }
     ]
 }
+

.openpublishing.redirection.json

@@ -9,7 +9,7 @@ manager: celestedg
 ms.service: active-directory
 ms.workload: identity
 ms.topic: conceptual
-ms.date: 06/06/2020
+ms.date: 10/01/2021
 ms.author: vigunase
 ms.subservice: B2C
 ---

.openpublishing.redirection.synapse-analytics.json

@@ -111,7 +111,7 @@ The **OutputClaim** element contains the following attributes:
 | ClaimTypeReferenceId | Yes | A reference to a ClaimType already defined in the ClaimsSchema section in the policy.
 | TransformationClaimType | Yes | An identifier to reference a transformation claim type. Each claim transformation has its own values. See the [claims transformation reference](#claims-transformations-reference) for a complete list of the available values. |
 
-If input claim and the output claim are the same type (string, or boolean), you can use the same input claim as the output claim. In this case, the claims transformation changes the input claim with the output value.
+Input and output claims used in claims transformation need to be distinct. The same input claim cannot be used as the output claim.
 
 ## Example
 

articles/active-directory-b2c/best-practices.md

@@ -59,7 +59,7 @@ Before you follow the procedures in this article, make sure that your computer i
 
 * [Visual Studio Code](https://code.visualstudio.com/) or another code editor.
 * [Node.js runtime](https://nodejs.org/en/download/) and [npm](https://docs.npmjs.com/downloading-and-installing-node-js-and-npm).
-* [Angular LCI](https://angular.io/cli).
+* [Angular CLI](https://angular.io/cli).
 
 ## Step 1: Configure your user flow
 

articles/active-directory-b2c/claimstransformations.md

@@ -8,7 +8,7 @@ manager: celestedg
 ms.service: active-directory
 ms.workload: identity
 ms.topic: how-to
-ms.date: 09/15/2021
+ms.date: 10/08/2021
 ms.custom: project-no-code
 ms.author: mimart
 ms.subservice: B2C
@@ -58,6 +58,11 @@ To configure your user flow token lifetime:
 1. Under **Token lifetime**, adjust the properties to fit the needs of your application.
 1. Click **Save**.
 
+
+
+:::image type="content" source="./media/configure-tokens/configure-tokens.png" alt-text="configure user flows tokens in Azure portal.":::
+
+
 ::: zone-end
 
 ::: zone pivot="b2c-custom-policy"