Merge pull request #181431 from MicrosoftDocs/master

11/30 OOB Publish

Author: huypub

.openpublishing.redirection.json

@@ -46923,7 +46923,77 @@
     },
     {
       "source_path_from_root": "/articles/communication-services/concepts/telephony-sms/sip-interface-infrastructure.md",
-      "redirect_url": "/azure/communication-services/concepts/telephony-sms/direct-routing-infrastructure",
+      "redirect_url": "/azure/communication-services/concepts/telephony/direct-routing-infrastructure",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/communication-services/concepts/telephony-sms/direct-routing-infrastructure.md",
+      "redirect_url": "/azure/communication-services/concepts/telephony/direct-routing-infrastructure",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/communication-services/concepts/telephony-sms/certified-session-border-controllers.md",
+      "redirect_url": "/azure/communication-services/concepts/telephony/certified-session-border-controllers",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/communication-services/concepts/telephony-sms/direct-routing-provisioning.md",
+      "redirect_url": "/azure/communication-services/concepts/telephony/direct-routing-provisioning",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/communication-services/concepts/telephony-sms/plan-solution.md",
+      "redirect_url": "/azure/communication-services/concepts/telephony/plan-solution",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/communication-services/concepts/telephony-sms/telephony-concept.md",
+      "redirect_url": "/azure/communication-services/concepts/telephony/telephony-concept",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/communication-services/concepts/telephony-sms/get-phone-number.md",
+      "redirect_url": "/azure/communication-services/concepts/telephony/get-phone-number",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/communication-services/concepts/telephony-sms/port-phone-number.md",
+      "redirect_url": "/azure/communication-services/concepts/telephony/port-phone-number",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/communication-services/concepts/telephony-sms/concepts.md",
+      "redirect_url": "/azure/communication-services/concepts/sms/concepts",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/communication-services/concepts/telephony-sms/messaging-policy.md",
+      "redirect_url": "/azure/communication-services/concepts/sms/messaging-policy",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/communication-services/concepts/telephony-sms/sdk-features.md",
+      "redirect_url": "/azure/communication-services/concepts/sms/sdk-features",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/communication-services/concepts/telephony-sms/sms-faq.md",
+      "redirect_url": "/azure/communication-services/concepts/sms/sms-faq",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/communication-services/quickstarts/telephony-sms/handle-sms-events.md",
+      "redirect_url": "/azure/communication-services/quickstarts/sms/handle-sms-events",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/communication-services/quickstarts/telephony-sms/logic-app.md",
+      "redirect_url": "/azure/communication-services/quickstarts/sms/logic-app",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/communication-services/quickstarts/telephony-sms/send.md",
+      "redirect_url": "/azure/communication-services/quickstarts/sms/send",
       "redirect_document_id": false
     },
     {

articles/active-directory/authentication/concept-password-ban-bad.md

@@ -203,10 +203,14 @@ Let's look a slightly different example to show how additional complexity in a p
 
 ## What do users see
 
-When a user attempts to reset a password to something that would be banned, the following error message is displayed:
+When a user attempts to reset or change a password to something that would be banned, one of the following error messages are displayed:
 
 *"Unfortunately, your password contains a word, phrase, or pattern that makes your password easily guessable. Please try again with a different password."*
 
+*"We've seen that password too many times before. Choose something harder to guess."*
+
+*"Choose a password that's harder for people to guess."*
+
 ## License requirements
 
 | Users | Azure AD Password Protection with global banned password list | Azure AD Password Protection with custom banned password list|

articles/active-directory/authentication/howto-password-ban-bad-on-premises-faq.yml

@@ -64,6 +64,12 @@ sections:
           
           Active Directory supports the ability to test a password to see if it passes the domain's current password complexity requirements, for example using the [NetValidatePasswordPolicy](/windows/win32/api/lmaccess/nf-lmaccess-netvalidatepasswordpolicy) api. When a password is validated in this way, the testing also includes validation by password-filter-dll based products such as Azure AD Password Protection - but the user names passed to a given password filter dll will be empty. In this scenario, Azure AD Password Protection will still validate the password using the currently in-effect password policy and will issue an event log message to capture the outcome, however the event log message will have empty user name fields.
           
+          ### I have hybrid users who attempt to change their password in Azure AD and receive the response "We've seen that password too many times before. Choose something harder to guess." In this case, why don't I see a validation attempt on-premises?
+          
+          When a hybrid user changes their password in Azure AD, whether through Azure AD SSPR, MyAccount, or another Azure AD password change mechanism, their password is evaluated against the global and custom banned password lists in the cloud. When the password reaches Active Directory through password-writeback, it has already been validated in Azure AD.
+          
+          Password resets and changes initiated in Azure AD that fail validation for hybrid users can be found in the Azure AD Audit logs. See [Troubleshoot self-service password reset in Azure Active Directory](/azure/active-directory/authentication/troubleshoot-sspr).
+          
           ### Is it supported to install Azure AD Password Protection side by side with other password-filter-based products?
           
           Yes. Support for multiple registered password filter dlls is a core Windows feature and not specific to Azure AD Password Protection. All registered password filter dlls must agree before a password is accepted.
@@ -312,4 +318,4 @@ additionalContent: |
   ## Next steps
   If you have an on-premises Azure AD Password Protection question that isn't answered here, submit a Feedback item below - thank you!
           
-  [Deploy Azure AD password protection](howto-password-ban-bad-on-premises-deploy.md)
+  [Deploy Azure AD password protection](howto-password-ban-bad-on-premises-deploy.md)

articles/active-directory/external-identities/conditional-access.md

@@ -6,7 +6,7 @@ services: active-directory
 ms.service: active-directory
 ms.subservice: B2B
 ms.topic: conceptual
-ms.date: 01/21/2020
+ms.date: 11/30/2021
 
 ms.author: mimart
 author: msmimart
@@ -69,18 +69,6 @@ The resource tenant is always responsible for Azure AD Multi-Factor Authenticati
 >[!NOTE]
 >Azure AD Multi-Factor Authentication is done at resource tenancy to ensure predictability. When the guest user signs in, they'll see the resource tenant sign-in page displayed in the background, and their own home tenant sign-in page and company logo in the foreground.
 
-### Set up Azure AD Multi-Factor Authentication for B2B users
-
-To set up Azure AD Multi-Factor Authentication for B2B collaboration users, watch this video:
-
->[!VIDEO https://channel9.msdn.com/Blogs/Azure/b2b-conditional-access-setup/Player]
-
-### B2B users Azure AD Multi-Factor Authentication for offer redemption
-
-To learn more about the Azure AD Multi-Factor Authentication redemption experience, watch this video:
-
->[!VIDEO https://channel9.msdn.com/Blogs/Azure/MFA-redemption/Player]
-
 ### Azure AD Multi-Factor Authentication reset for B2B users
 
 Now, the following PowerShell cmdlets are available to proof up B2B guest users:
@@ -118,7 +106,8 @@ There are various factors that influence CA policies for B2B guest users.
 In CA, there's an option to require a user’s [device to be Compliant or Hybrid Azure AD joined](../conditional-access/concept-conditional-access-conditions.md#device-state-preview). B2B guest users can only satisfy compliance if the resource tenant can manage their device. Devices cannot be managed by more than one organization at a time. B2B guest users can't satisfy the Hybrid Azure AD join because they don't have an on-premises AD account. 
 
 >[!Note]
->It is not recommended to require a managed device for external users.
+>- It is not recommended to require a managed device for external users.
+>- When guest users try to access a resource protected by Conditional Access, they'll no longer be asked to re-register their devices in your tenant. Previously, guest users would be able to start the re-registration process. However, this would remove their existing device registration, and they'd be unable to complete registration. Now, they'll see a Conditional Access blocking page to prevent them from trying to re-register their devices.
 
 ### Mobile application management policies
 

articles/active-directory/hybrid/reference-connect-version-history.md

@@ -63,7 +63,7 @@ Required permissions | For permissions required to apply an update, see [account
 > [!NOTE]
 > This is an update release of Azure AD Connect. This version is intended to be used by customers who are running an older version of Windows Server and cannot upgrade their server to Windows Server 2016 or newer at this time. You cannot use this version to update an Azure AD Connect V2.0 server.
 >
-> This release is not supported on Windows Server 2016 or newer. This release includes SQL Server 2012 components and will be retired on August 31st 2022. You will need to upgrade your Server OS and AADConnect version before that date.
+> This release should not be installed on Windows Server 2016 or newer. This release includes SQL Server 2012 components and will be retired on August 31st 2022. You will need to upgrade your Server OS and AADConnect version before that date.
 >
 > There is an issue where upgrading to this v1.6 build or any newer builds resets the group membership limit to 50k. When a server is upgraded to this build, or any newer 1.6 builds, then the customer should reapply the rules changes they applied when initially increasing the group membership limit to 250k before they enable sync for the server. 
 

articles/active-directory/saas-apps/github-enterprise-managed-user-provisioning-tutorial.md

@@ -22,6 +22,8 @@ ms.author: thwimmer
 
 This tutorial describes the steps you need to perform in both GitHub Enterprise Managed User and Azure Active Directory (Azure AD) to configure automatic user provisioning. When configured, Azure AD automatically provisions and de-provisions users and groups to GitHub Enterprise Managed User using the Azure AD Provisioning service. For important details on what this service does, how it works, and frequently asked questions, see [Automate user provisioning and deprovisioning to SaaS applications with Azure Active Directory](../app-provisioning/user-provisioning.md).
 
+> [!NOTE]
+> [GitHub Enterprise Managed Users](https://docs.github.com/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users) is a feature of GitHub Enterprise Cloud which is different from GitHub Enterprise's standard SAML SSO and user provisioning implementation. If you haven't specifically requested EMU instance, you have standard GitHub Enterprise Cloud plan. In that case, please refer to [the documentation](https://docs.microsoft.com/azure/active-directory/saas-apps/github-provisioning-tutorial) to configure user provisioning in your non-EMU organisation. User provisioning is not supported for [GitHub Enteprise Accounts](https://docs.github.com/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)
 
 ## Capabilities Supported
 > [!div class="checklist"]
@@ -172,4 +174,4 @@ Once you've configured provisioning, use the following resources to monitor your
 
 ## Next steps
 
-* [Learn how to review logs and get reports on provisioning activity](../app-provisioning/check-status-user-account-provisioning.md)
+* [Learn how to review logs and get reports on provisioning activity](../app-provisioning/check-status-user-account-provisioning.md)

articles/active-directory/saas-apps/github-enterprise-managed-user-tutorial.md

@@ -22,6 +22,10 @@ In this tutorial, you'll learn how to integrate GitHub Enterprise Managed User (
 * Enable your users to be automatically signed-in to GitHub Enterprise Managed User with their Azure AD accounts.
 * Manage your accounts in one central location - the Azure portal.
 
+> [!NOTE]
+> [GitHub Enterprise Managed Users](https://docs.github.com/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users) is a feature of GitHub Enterprise Cloud which is different from GitHub Enterprise's standard SAML SSO implementation. If you haven't specifically requested EMU instance, you have standard GitHub Enterprise Cloud plan. In that case, please refer to relevant documentation to configure your non-EMU [organisation](https://docs.microsoft.com/azure/active-directory/saas-apps/github-tutorial) or [enterprise account](https://docs.microsoft.com/azure/active-directory/saas-apps/github-enterprise-cloud-enterprise-account-tutorial) to authenticate with Azure Active Directory.
+
+
 ## Prerequisites
 
 To get started, you need the following items: