Merge branch 'main' into java-quickstart

Author: cephalin

.openpublishing.publish.config.json

@@ -1215,6 +1215,7 @@
   ".openpublishing.redirection.container-service.json",
   ".openpublishing.redirection.defender-for-cloud.json",
   ".openpublishing.redirection.defender-for-iot.json",
+  ".openpublishing.redirection.guidance.json",
   ".openpublishing.redirection.iot-hub-device-update.json",
   ".openpublishing.redirection.key-vault.json",
   ".openpublishing.redirection.machine-configuration.json",
@@ -1233,6 +1234,7 @@
   "articles/ai-services/.openpublishing.redirection.cognitive-services.json",
   "articles/ai-studio/.openpublishing.redirection.ai-studio.json",
   "articles/azure-fluid-relay/.openpublishing.redirection.fluid-relay.json",
+  "articles/azure-functions/.openpublishing.redirection.azure-functions.json",
   "articles/azure-netapp-files/.openpublishing.redirection.azure-netapp-files.json",
   "articles/azure-relay/.openpublishing.redirection.relay.json",
   "articles/azure-video-analyzer/.openpublishing.redirection.azure-video-analyzer.json",

.openpublishing.redirection.azure-monitor.json

@@ -2287,17 +2287,17 @@
         },
         {
             "source_path_from_root": "/articles/azure-monitor/insights/solutions-inventory.md",
-            "redirect_url": "/azure/azure-monitor/monitor-reference",
+            "redirect_url": "/azure/azure-monitor/overview",
             "redirect_document_id": false
         },
         {
             "source_path_from_root": "/articles/monitoring/monitoring-solutions-inventory.md",
-            "redirect_url": "/azure/azure-monitor/monitor-reference",
+            "redirect_url": "/azure/azure-monitor/overview",
             "redirect_document_id": false
         },
         {
             "source_path_from_root": "/articles/azure-monitor/platform/data-locations.md",
-            "redirect_url": "/azure/azure-monitor/monitor-reference/",
+            "redirect_url": "/azure/azure-monitor/overview/",
             "redirect_document_id": false
         },
         {
@@ -5146,7 +5146,7 @@
         },
         {
             "source_path_from_root": "/articles/azure-monitor/platform/partners.md",
-            "redirect_url": "/azure/azure-monitor//partners",
+            "redirect_url": "/azure/azure-monitor/overview#integrate",
             "redirect_document_id": false
         },
         {
@@ -6598,6 +6598,16 @@
             "source_path_from_root": "/articles/azure-monitor/app/java-standalone-arguments.md",
             "redirect_url": "/azure/azure-monitor/app/java-get-started-supplemental",
             "redirect_document_id": true
+        },
+        {
+            "source_path_from_root": "/articles/azure-monitor/partners.md",
+            "redirect_url": "/azure/azure-monitor/overview#integrate",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-monitor/monitor-reference.md",
+            "redirect_url": "/azure/azure-monitor/overview",
+            "redirect_document_id": false
         }
     ]
 }

.openpublishing.redirection.guidance.json

@@ -108,6 +108,7 @@ The following table lists the claim resolvers with information about the OpenID
 | {OIDC:Resource} |The `resource`  query string parameter. | N/A |
 | {OIDC:Scope} |The `scope`  query string parameter. | openid |
 | {OIDC:Username}| The [resource owner password credentials flow](add-ropc-policy.md) user's username.| [email protected]|
+| {OIDC:IdToken} | The `id token`  query string parameter. | N/A |
 
 Check out the [Live demo](https://github.com/azure-ad-b2c/unit-tests/tree/main/claims-resolver#openid-connect-relying-party-application) of the OpenID Connect claim resolvers.
 

.openpublishing.redirection.json

@@ -379,7 +379,7 @@ Follow the steps in [Upload custom policy file](custom-policies-series-hello-wor
 
 ## Step 7 - Validate user input by using validation technical profiles
 
-The validation techniques we've used in step 1, step 2 and step 3 aren't applicable for all scenarios. If your business rules are complex to be defined at claim declaration level, you can configure a [Validation Technical](validation-technical-profile.md), and then call it from a [Self-Asserted Technical Profile](self-asserted-technical-profile.md).
+The validation techniques we've used in step 1, step 2 and step 3 aren't applicable for all scenarios. If your business rules are too complex to be defined at claim declaration level, you can configure a [Validation Technical](validation-technical-profile.md), and then call it from a [Self-Asserted Technical Profile](self-asserted-technical-profile.md).
 
 > [!NOTE] 
 > Only self-asserted technical profiles can use validation technical profiles. Learn more about [validation technical profile](validation-technical-profile.md) 

.openpublishing.redirection.machine-configuration.json

@@ -13,9 +13,7 @@ metadata:
   ms.author: celested
   ms.service: active-directory
   ms.subservice: azuread-dev
-  ms.workload: identity
   ROBOTS: NOINDEX
-
 landingContent:
   - title: Azure Active Directory for developers
     linkLists: