You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As documented in the described document, company branding, through its feature sign-in page text I should be capable of
adding a text that appears on the bottom of the sign-in page. Quoting the document: "You can use this text to communicate additional information, such as the phone number to your help desk or a legal statement". I've followed the steps for adding such text without success, when I run the user flow, there is not such text. I even tried to write a random plain text for testing and still don't work. To my understanding of documentation, such text should look like this: Sign-in page text. I really hope help with this matter.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
ID: 72f2e675-436d-dcd4-fa27-49408b201158
Version Independent ID: 4d821732-fc10-f4a6-3c7d-77bce75299d7
@JMRMEDEV The sign-in page text is displayed only at login.microsoftonline.com and not when you run a B2C User Flow. The reason is, Company Branding inserts only below piece of information in the User Flow HTML page:
As documented in the described document, company branding, through its feature sign-in page text I should be capable of
adding a text that appears on the bottom of the sign-in page. Quoting the document: "You can use this text to communicate additional information, such as the phone number to your help desk or a legal statement". I've followed the steps for adding such text without success, when I run the user flow, there is not such text. I even tried to write a random plain text for testing and still don't work. To my understanding of documentation, such text should look like this: Sign-in page text. I really hope help with this matter.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: