Merge pull request #107481 from MicrosoftDocs/master

3/12 AM Publish

Author: huypub

articles/active-directory-b2c/custom-policy-password-complexity.md

@@ -149,4 +149,4 @@ To configure the password complexity, override the `newPassword` and `reenterPas
 ## Next steps
 
 - Learn how to [Configure password change using custom policies in Azure Active Directory B2C](custom-policy-password-change.md).
-- - Learn more about the [Predicates](predicates.md) and [PredicateValidations](predicates.md#predicatevalidations) elements in the IEF reference.
+- Learn more about the [Predicates](predicates.md) and [PredicateValidations](predicates.md#predicatevalidations) elements in the IEF reference.

articles/active-directory/app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md

@@ -98,7 +98,8 @@ Scoping filters are configured as part of the attribute mappings for each Azure
 
 
 >[!IMPORTANT] 
-> The IsMemberOf filter is not supported currently.
+> - The IsMemberOf filter is not supported currently.
+> - EQUALS and NOT EQUALS are not supported for multi-valued attributes
 
 9. Optionally, repeat steps 7-8 to add more scoping clauses.
 

articles/active-directory/b2b/b2b-quickstart-invite-powershell.md

@@ -78,7 +78,7 @@ When prompted, enter your credentials.
 1. To send an invitation to your test email account, run the following PowerShell command (replace **"Sanda"** and **sanda\@fabrikam.com** with your test email account name and email address): 
 
    ```powershell
-   New-AzureADMSInvitation -InvitedUserDisplayName "Sanda" -InvitedUserEmailAddress [email protected] -InviteRedirectURL https://myapps.azure.com -SendInvitationMessage $true
+   New-AzureADMSInvitation -InvitedUserDisplayName "Sanda" -InvitedUserEmailAddress [email protected] -InviteRedirectURL https://myapps.microsoft.com -SendInvitationMessage $true
    ```
 2. The command sends an invitation to the email address specified. Check the output, which should look similar to the following:
 

articles/active-directory/develop/authentication-scenarios.md

@@ -47,9 +47,9 @@ Azure AD also provides Azure Active Directory B2C so that organizations can sign
 
 Security tokens contain information about users and apps. Azure AD uses JSON based tokens (JWTs) that contain claims.
 
-A claim provides assertions about one entity, such as a [client application](https://docs.microsoft.com/azure/active-directory/develop/developer-glossary#client-application) or [resource owner](https://docs.microsoft.com/azure/active-directory/develop/developer-glossary#resource-owner)), to another entity, such as a [resource server](https://docs.microsoft.com/azure/active-directory/develop/developer-glossary#resource-server)).
+A claim provides assertions about one entity, such as a [client application](https://docs.microsoft.com/azure/active-directory/develop/developer-glossary#client-application) or [resource owner](https://docs.microsoft.com/azure/active-directory/develop/developer-glossary#resource-owner), to another entity, such as a [resource server](https://docs.microsoft.com/azure/active-directory/develop/developer-glossary#resource-server).
 
-Claims are name/value pairs that relay facts about the token subject. For example, a claim may contain facts about the security principal that was authenticated by the [authorization server](https://docs.microsoft.com/azure/active-directory/develop/developer-glossary#authorization-server)). The claims present in a given token  depend on many things, including the type of token, the type of credential used to authenticate the subject, the application configuration, and so on.
+Claims are name/value pairs that relay facts about the token subject. For example, a claim may contain facts about the security principal that was authenticated by the [authorization server](https://docs.microsoft.com/azure/active-directory/develop/developer-glossary#authorization-server). The claims present in a given token  depend on many things, including the type of token, the type of credential used to authenticate the subject, the application configuration, and so on.
 
 Applications can use claims for various tasks such as:
 

articles/active-directory/manage-apps/change-name-or-logo-portal.md

@@ -37,7 +37,7 @@ It's easy to change the name or logo for a custom enterprise application in Azur
 7. In the file picker, select the file you want as the new logo. The name of the file appears in the box below the current logo image.
 
    > [!NOTE]
-   > Azure requires the logo image to be a PNG file, and it applies limits on width, height, and file size.
+   > Azure requires the logo image to be a PNG file, and it applies limits on width, height, and file size. Custom logos must be exactly 215 × 215 pixels in size and be in PNG format. We recommend that you use a solid color background with no transparency in your application logo to appear best to users.
 8. Select **Save**. If you chose a new logo, the **Logo** field's image changes to reflect the new logo file.
 
 ## Next steps

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

@@ -23,9 +23,8 @@ ms.collection: M365-identity-device-management
 
 In this tutorial, you'll learn how to integrate GitHub with Azure Active Directory (Azure AD). When you integrate GitHub with Azure AD, you can:
 
-* Control in Azure AD who has access to GitHub.
-* Enable your users to be automatically signed-in to GitHub with their Azure AD accounts.
-* Manage your accounts in one central location - the Azure portal.
+* Control in Azure AD who has access to your GitHub Enterprise Cloud Organization.
+* Manage access to your GitHub Enterprise Cloud Organization in one central location - the Azure portal.
 
 To learn more about SaaS app integration with Azure AD, see [What is application access and single sign-on with Azure Active Directory](https://docs.microsoft.com/azure/active-directory/active-directory-appssoaccess-whatis).
 
@@ -42,7 +41,7 @@ In this tutorial, you configure and test Azure AD single sign-on in a test envir
 
 * GitHub supports **SP** initiated SSO
 
-* GitHub supports [**Automated** user provisioning](github-provisioning-tutorial.md)
+* GitHub supports [**Automated** user provisioning (organization invitations)](github-provisioning-tutorial.md)
 * Once you configure GitHub you can enforce Session control, which protect exfiltration and infiltration of your organization’s sensitive data in real-time. Session control extend from Conditional Access. [Learn how to enforce session control with Microsoft Cloud App Security](https://docs.microsoft.com/cloud-app-security/proxy-deployment-aad)
 
 ## Adding GitHub from the gallery