Merge branch 'main' into patch-40

Author: JackStromberg

.openpublishing.redirection.json

@@ -22629,6 +22629,41 @@
       "redirect_url": "/azure/active-directory/conditional-access/concept-conditional-access-cloud-apps",
       "redirect_document_id": true
     },
+    {
+      "source_path_from_root": "/articles/scheduler/scheduler-advanced-complexity.md",
+      "redirect_url": "/azure/scheduler/migrate-from-scheduler-to-logic-apps",
+      "redirect_document_id": ""
+    },
+    {
+      "source_path_from_root": "/articles/scheduler/scheduler-concepts-terms.md",
+      "redirect_url": "/azure/scheduler/migrate-from-scheduler-to-logic-apps",
+      "redirect_document_id": ""
+    },
+    {
+      "source_path_from_root": "/articles/scheduler/scheduler-powershell-reference.md",
+      "redirect_url": "/azure/scheduler/migrate-from-scheduler-to-logic-apps",
+      "redirect_document_id": ""
+    },
+    {
+      "source_path_from_root": "/articles/scheduler/scheduler-plans-billing.md",
+      "redirect_url": "/azure/scheduler/migrate-from-scheduler-to-logic-apps",
+      "redirect_document_id": ""
+    },
+    {
+      "source_path_from_root": "/articles/scheduler/scheduler-limits-defaults-errors.md",
+      "redirect_url": "/azure/scheduler/migrate-from-scheduler-to-logic-apps",
+      "redirect_document_id": ""
+    },
+    {
+      "source_path_from_root": "/articles/scheduler/scheduler-high-availability-reliability.md",
+      "redirect_url": "/azure/scheduler/migrate-from-scheduler-to-logic-apps",
+      "redirect_document_id": ""
+    },
+    {
+      "source_path_from_root": "/articles/scheduler/scheduler-outbound-authentication.md",
+      "redirect_url": "/azure/scheduler/migrate-from-scheduler-to-logic-apps",
+      "redirect_document_id": ""
+    },
     {
       "source_path_from_root": "/articles/scheduler/get-started-portal.md",
       "redirect_url": "/azure/scheduler/migrate-from-scheduler-to-logic-apps",
@@ -26254,9 +26289,19 @@
       "redirect_url": "/azure/storage/blobs/storage-quickstart-blobs-nodejs",
       "redirect_document_id": false
     },
+    {
+      "source_path_from_root": "/articles/storage/blobs/storage-quickstart-blobs-javascript-client-libraries-legacy.md",
+      "redirect_url": "/azure/storage/blobs/quickstart-blobs-javascript-browser",
+      "redirect_document_id": false
+    },    
+    {
+      "source_path_from_root": "/articles/storage/blobs/storage-quickstart-blobs-nodejs-legacy.md",
+      "redirect_url": "/azure/storage/blobs/storage-quickstart-blobs-nodejs",
+      "redirect_document_id": false
+    },        
     {
       "source_path_from_root": "/articles/storage/blobs/storage-quickstart-blobs-nodejs-v10.md",
-      "redirect_url": "/azure/storage/blobs/storage-quickstart-blobs-nodejs-legacy",
+      "redirect_url": "/azure/storage/blobs/storage-quickstart-blobs-nodejs",
       "redirect_document_id": false
     },
     {

.openpublishing.redirection.media-services.json

@@ -624,6 +624,11 @@
             "source_path_from_root": "/articles/media-services/latest/security-private-link-how-to.md",
             "redirect_url": "/azure/media-services/latest/security-private-link-arm-how-to",
             "redirect_document_id": false
+          },
+          {
+            "source_path_from_root": "/articles/media-services/latest/asset-create-asset-upload-portal-quickstart.md",
+            "redirect_url": "/azure/media-services/latest/video-on-demand-simple-portal-quickstart",
+            "redirect_document_id": true
           },     
         {
             "source_path_from_root": "/articles/media-services/latest/latest/questions-collection.md",

articles/active-directory/authentication/howto-authentication-passwordless-security-key-on-premises.md

@@ -17,7 +17,7 @@ ms.collection: M365-identity-device-management
 ---
 # Enable passwordless security key sign-in to on-premises resources by using Azure AD 
 
-This document discusses how to enable passwordless authentication to on-premises resources for environments with both *Azure Active Directory (Azure AD)-joined* and *hybrid Azure AD-joined* Windows 10 devices. This passwordless authentication functionality provides seamless single sign-on (SSO) to on-premises resources when you use Microsoft-compatible security keys.
+This document discusses how to enable passwordless authentication to on-premises resources for environments with both *Azure Active Directory (Azure AD)-joined* and *hybrid Azure AD-joined* Windows 10 devices. This passwordless authentication functionality provides seamless single sign-on (SSO) to on-premises resources when you use Microsoft-compatible security keys, or with [Windows Hello for Business Cloud trust](/windows/security/identity-protection/hello-for-business/hello-hybrid-cloud-trust.md)
 
 ## Use SSO to sign in to on-premises resources by using FIDO2 keys
 
@@ -44,11 +44,6 @@ You must also meet the following system requirements:
 
 - Devices must be running Windows 10 version 2004 or later.
 
-- You must be running [Azure AD Connect version 1.4.32.0 or later](../hybrid/how-to-connect-install-roadmap.md#install-azure-ad-connect).
-  - For more information about the available Azure AD hybrid authentication options, see the following articles:
-    - [Choose the right authentication method for your Azure AD hybrid identity solution](../hybrid/choose-ad-authn.md)
-    - [Select which installation type to use for Azure AD Connect](../hybrid/how-to-connect-install-select-installation.md)
-
 - Your Windows Server domain controllers must have patches installed for the following servers:
     - [Windows Server 2016](https://support.microsoft.com/help/4534307/windows-10-update-kb4534307)
     - [Windows Server 2019](https://support.microsoft.com/help/4534321/windows-10-update-kb4534321)

articles/active-directory/develop/active-directory-saml-claims-customization.md

@@ -121,7 +121,7 @@ You can use the following functions to transform claims.
 | Function | Description |
 |----------|-------------|
 | **ExtractMailPrefix()** | Removes the domain suffix from either the email address or the user principal name. This extracts only the first part of the user name being passed through (for example, "joe_smith" instead of [email protected]). |
-| **Join()** | Creates a new value by joining two attributes. Optionally, you can use a separator between the two attributes. |
+| **Join()** | Creates a new value by joining two attributes. Optionally, you can use a separator between the two attributes. For NameID claim transformation, the Join() function has specific behaviour when the transformation input has a domain part. It will remove the domain part from input before joining it with the separator and the selected parameter. For example, if the input of the transformation is ‘[email protected]’ and the separator is ‘@’ and the parameter is ‘fabrikam.com’, this will result in [email protected]. |
 | **ToLowercase()** | Converts the characters of the selected attribute into lowercase characters. |
 | **ToUppercase()** | Converts the characters of the selected attribute into uppercase characters. |
 | **Contains()** | Outputs an attribute or constant if the input matches the specified value. Otherwise, you can specify another output if there’s no match.<br/>For example, if you want to emit a claim where the value is the user’s email address if it contains the domain “@contoso.com”, otherwise you want to output the user principal name. To do this, you would configure the following values:<br/>*Parameter 1(input)*: user.email<br/>*Value*: "@contoso.com"<br/>Parameter 2 (output): user.email<br/>Parameter 3 (output if there's no match): user.userprincipalname |