A cloud-based identity and access management service for securing user authentication and resource access
Hi @ilmi rf,
This behavior is expected in certain Azure AD B2C scenarios and is usually related to how company branding is applied and cached across different B2C sign‑in experiences.
Why the old logo is still shown
- Branding applies per user flow / policy In Azure AD B2C, company branding (banner logo, background image, background color) is applied per user flow. Updating the logo under Azure AD B2C → Company branding does not automatically refresh all existing user flows unless they are explicitly configured to use company branding. Microsoft documents that branding must be enabled and associated with the specific user flow being used for sign‑in. [learn.microsoft.com]
- Caching of branding assets Azure AD B2C sign‑in pages cache branding assets (logos and images). Because of this, updates may not appear immediately, especially if the same browser, session, or URL parameters are reused. This is a known and documented behavior for B2C UI rendering. [learn.microsoft.com]
- Custom HTML or custom policies If the sign‑in experience uses custom HTML or custom policies, the uploaded company branding logo is not automatically rendered unless the page explicitly references the tenant branding assets. Microsoft confirms that custom pages must opt in to tenant branding using the supported attributes (for example,
data-tenant-branding-logo). [stackoverflow.com]
What you should verify
- Confirm that the correct user flow is being used by the application and that company branding is enabled for that flow. [learn.microsoft.com]
- If using custom HTML or custom policies, ensure the page is configured to consume tenant branding assets; otherwise, the default or previously embedded logo will continue to appear. [stackoverflow.com]
- Test the sign‑in page in a private/incognito browser session or with a modified policy URL to rule out cached content, as branding images are served via CDN and cached by design. [learn.microsoft.com]
Reference documentation
- Customize the user interface in Azure AD B2C (company branding and user flows): https://learn.microsoft.com/azure/active-directory-b2c/customize-ui
- Customize the UI with HTML templates (branding behavior and caching): https://learn.microsoft.com/azure/active-directory-b2c/customize-ui-with-html
- Use company branding assets in custom policies: https://learn.microsoft.com/azure/active-directory-b2c/customize-ui-with-html#use-company-branding-assets-in-custom-html
If the issue persists after confirming the above, it is recommended to re‑save the user flow, re‑upload the logo, and retest using a fresh session, as branding updates are not always reflected instantly due to caching.
Hope this helps clarify the behavior,if not, please let us know.