Azure-docs: Document the prompt parameter

[spottedmahn]

When requesting a token there is a prompt parameter to control:

The type of user interaction that is required.

This parameter is not documented though. What are all the options?

I know of:

• select_account
• login
• none

There are some references to the parameter like here: OAuth 2.0 authorization code flow: Use an edit-profile policy.

---

Maybe it could be documented under the reference section?

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 245ef8a4-a811-19b7-676c-aa9b82e2126f
• Version Independent ID: ad2ec743-2aa7-b3c7-3350-2986a78d7c90
• Content: Cloud identity management web and mobile apps Azure AD B2C | Microsoft Docs
• Content Source: articles/active-directory-b2c/active-directory-b2c-overview.md
• Service: active-directory-b2c
• GitHub Login: @SaeedAkhter-MSFT
• Microsoft Alias: saeedakhter-msft

[BryanTrach-MSFT]

Thanks for the feedback! We are currently investigating and will update you shortly.

[MohitGargMSFT]

I have assigned the issue to the author to investigate and update as appropriate.

[spottedmahn]

Another example of having this documented would help: Xamarin.Forms app using Azure AD B2C only showing Microsoft login

[parakhj]

@MohitGargMSFT how do I change who this issue is assigned to? I need to assign it to myself

[MohitGargMSFT]

@parakhj I have assigned this issue to you. Thanks.

[parakhj]

@spottedmahn the parameters are the same ones that are in the OIDC spec. It could help to restate them in our documentation, but i'm not sure how that will help resolve the stack overflow post that you linked. How is that issue related to the prompt parameter?

[spottedmahn]

Hey @parakhj - oh, I see. Found it: 3.1.2.1. Authentication Request -> prompt

• none
• login
• consent
• select_account

---

I think it would help to state them in the B2C documentation to describe how B2C behaves. For example, in a web app, if the user is signed already and the cookie is still valid, the user will not have to login again and the token(s) will be returned.

Another example, when you use the "run now" feature in the portal, it sets the prompt parameter to select_account, therefore, preventing the cookie from taking effect.

---

It relates to the SO post in that the fix was UIBehavior.SelectAccount which made the IDPs show up.

[spottedmahn]

Another SO post related to the prompt parameter: Azure AD B2C password change custom policy, user needs to sign in every time

[davidmu1]

@spottedmahn We understand that the prompt parameter is currently defined in the OIDC spec, but could be more thoroughly described in context to B2C. We have opened an item in our documentation backlog to have this investigated and updated. We'll respond back to you on this issue when we've done the work. For now, we'll close this GitHub issue.

please-close

[davidmu1]

@spottedmahn Michael, you seem very invested in B2C docs, I would love to talk with you about how the docs might be improved and what you think. Give me a shout at [email protected] if you can spare a few minutes. Thanks.

[spottedmahn]

Another instance of the prompt parameter: Azure B2C single sign On Doesn't work

if you want to leverage the SSO function, we shouldn't pass the prompt parameter with value select_account

[davidmu1]

@spottedmahn Very useful for when we improve our description of the prompt parameter. Thanks!