Branding update.

Author: csmulligan

articles/active-directory/external-identities/external-collaboration-settings-configure.md

@@ -29,6 +29,7 @@ External collaboration settings let you specify what roles in your organization
 - **Allow or block domains**: You can use collaboration restrictions to allow or deny invitations to the domains you specify. For details, see [Allow or block domains](allow-deny-list.md).
 
 For B2B collaboration with other Azure AD organizations, you should also review your [cross-tenant access settings](cross-tenant-access-settings-b2b-collaboration.md) to ensure your inbound and outbound B2B collaboration and scope access to specific users, groups, and applications.
+For B2B collaboration end-users who perform cross-tenant sign-ins, their home tenant branding appears, even if there isn't custom branding specified.
 
 ## Configure settings in the portal
 
@@ -96,13 +97,6 @@ Add-MsolRoleMember -RoleObjectId 95e79109-95c0-4d8e-aee3-d01accf2d47b -RoleMembe
 
 When a B2B user signs into a resource tenant to collaborate, a sign-in log is generated in both the home tenant and the resource tenant. These logs include information such as the application being used, email addresses, tenant name, and tenant ID for both the home tenant and the resource tenant. 
 
-## B2B collaboration branding changes
-
-Starting from September 30, 2023, when B2B collaboration end-users perform cross-tenant sign-ins, they'll notice a change in branding. Instead of seeing the resource tenant's branding, it will show their home tenant branding, even if there isn't custom branding specified. 
-We're making this change to highlight that the user is signing into their home account. No action is needed from you to enable this change.
-
-:::image type="content" source="media/external-identities-overview/placeholder.png" alt-text="Placeholder alt text."::: 
-
 ## Next steps
 
 See the following articles on Azure AD B2B collaboration:

articles/active-directory/external-identities/external-identities-overview.md

@@ -145,12 +145,7 @@ When you're considering B2B collaboration with a specific external Azure AD orga
 
 - **Example 2**: You allow B2B collaboration with Fabrikam in your cross-tenant access settings, but then you add `fabrikam.com` to your blocked domains in your external collaboration settings. Your users won't be able to invite new Fabrikam guest users, but existing Fabrikam guests will be able to continue using B2B collaboration.
 
-### B2B collaboration branding changes
-
-Starting from September 30, 2023, when B2B collaboration end-users perform cross-tenant sign-ins, they'll notice a change in branding. Instead of seeing the resource tenant's branding, it will show their home tenant branding, even if there isn't custom branding specified. 
-We're making this change to highlight that the user is signing into their home account. No action is needed from you to enable this change.
-
-:::image type="content" source="media/external-identities-overview/placeholder.png" alt-text="Placeholder alt text."::: 
+For B2B collaboration end-users who perform cross-tenant sign-ins, their home tenant branding appears, even if there isn't custom branding specified.
 
 ### Azure Active Directory B2C management