Azure-docs: document may not be correct

[Calvin-Yuhui-Liu]

3 issues:

1. About “Register the IdentityExperienceFramework application” and “Register the ProxyIdentityExperienceFramework application”, both have instruction for “Under Supported account types, select Accounts in this organizational directory only”. However if you do so, the application is not a B2C application and will not be available to choose in user flow. Please refer to this discussion.
2. About “Test the custom policy”, it should be “user flow”.
3. It asks to test _webapp1_ but there's no webapp1.

---

Document Details

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

• ID: bee63035-00ee-f7fd-97a1-69dae5f808ef
• Version Independent ID: a3447928-73cc-0290-6d46-b89234757e3b
• Content: Get started with custom policies - Azure AD B2C
• Content Source: articles/active-directory-b2c/custom-policy-get-started.md
• Service: active-directory
• Sub-service: b2c
• GitHub Login: @msmimart
• Microsoft Alias: mimart

[AjayKumar-MSFT]

@Calvin-Yuhui-Liu, Thanks for the feedback! We are taking a look into this and will get back to you soon.

[souravmishra-msft]

@msmimart, Can you please look into this doc-update request.

[mmacy]

reassign:mmacy

Hi @Calvin-Yuhui-Liu, here are responses to your questions:

1. About “Register the IdentityExperienceFramework application” and “Register the ProxyIdentityExperienceFramework application”, both have instruction for “Under Supported account types, select Accounts in this organizational directory only”. However if you do so, the application is not a B2C application and will not be available to choose in user flow. Please refer to this discussion.

In this case, the application registrations should be configured as described in the article. These two applications are used by the Azure AD B2C back-end for manipulation of local user accounts. Your applications do not use these two registrations directly. Register them as described in the article.

1. About “Test the custom policy”, it should be “user flow”.

It is indeed custom policy. In the section above, Upload the policies, you upload the SignUpOrSignin.xml which contains the specified policy:

https://github.com/Azure-Samples/active-directory-b2c-custom-policy-starterpack/blob/master/SocialAndLocalAccounts/SignUpOrSignin.xml#L8

1. It asks to test _webapp1_ but there's no webapp1.

As listed in the Prerequisites section, the second bullet specifies:

• Register your application in the tenant that you created so that it can communicate with Azure AD B2C.

In that article, you register an application that you name webapp1. If you named it differently when completing the steps in that article, use the name you specified instead of webapp1.

[Calvin-Yuhui-Liu]

Hi Marsh,

Thanks for following up. I knew I was wrong for the 2nd and 3rd issue. But I'm still confused about the 1st one. I'll check it again. Thanks.

Best regards,
Calvin

---

From: Marsh Macy [e-mail]
Sent: Tuesday, May 26, 2020 10:24 AM
To: MicrosoftDocs/azure-docs [e-mail]
Cc: Calvin Liu [e-mail]; Mention [e-mail]
Subject: Re: [MicrosoftDocs/azure-docs] document may not be correct (#55576)

reassign:mmacy

Hi @Calvin-Yuhui-Liuhttps://github.com/Calvin-Yuhui-Liu, here are responses to your questions:

1. About “Register the IdentityExperienceFramework application” and “Register the ProxyIdentityExperienceFramework application”, both have instruction for “Under Supported account types, select Accounts in this organizational directory only”. However if you do so, the application is not a B2C application and will not be available to choose in user flow. Please refer to this discussionhttps://github.com/MicrosoftDocs/azure-docs/issues/51826.

In this case, the application registrations should be configured as described in the article. These two applications are used by the Azure AD B2C back-end for manipulation of local user accounts. Your applications do not use these two registrations directly. Register them as described in the article.

1. About “Test the custom policy”, it should be “user flow”.

It is indeed custom policy. In the section above, Upload the policieshttps://docs.microsoft.com/en-us/azure/active-directory-b2c/custom-policy-get-started?tabs=app-reg-preview#upload-the-policies, you upload the SignUpOrSignin.xml which contains the specified policy:

https://github.com/Azure-Samples/active-directory-b2c-custom-policy-starterpack/blob/master/SocialAndLocalAccounts/SignUpOrSignin.xml#L8

1. It asks to test webapp1 but there's no webapp1.

As listed in the Prerequisiteshttps://docs.microsoft.com/en-us/azure/active-directory-b2c/custom-policy-get-started?tabs=app-reg-preview#prerequisites section, the second bullet specifies:

• Register your application in the tenant that you created so that it can communicate with Azure AD B2C.

In that article, you register an application that you name webapp1. If you named it differently when completing the steps in that article, use the name you specified instead of webapp1.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/55576#issuecomment-634163893, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AKD27PTS4LCLOIJQYYRD2BTRTP3NXANCNFSM4NJKYFUA.

[PRMerger13]

Only Microsoft employees can manage issues via commenting in this repo.

[mmacy]

@Calvin-Yuhui-Liu This is indeed one of the more challenging things to set up in Azure AD B2C. The good news is that you only need to register those two applications once, so it's "set-it-and-forget-it" once you have them created (and assuming they're configured as described in the article).

[mmacy]

Hi @Calvin-Yuhui-Liu, checking in to see how it's going on this issue. If you're all set, let us know and we can close it out. Otherwise, let us know what additional information you require and we can work through it.

[mmacy]

Hi @Calvin-Yuhui-Liu, I'm going to request that this issue be closed as no doc updates are currently required. As mentioned in https://github.com/MicrosoftDocs/azure-docs/issues/55576#issuecomment-635457717, if you have further questions, please let us know.

please-close

[jarekkoziol]

@mmacy thanks for explanation. I think, that problem with this doc is that it is not implicite explained, that these 2 registrations (ProxyIdentityExperienceFramework and IdentityExperienceFramework ) are for internal policies use, so I was thinking that these should be my e.g. front end and backend app. I suggest to add your explanation to document.

[mmacy]

@jarekkoziol Agreed. I'll take a crack at better explaining the "for internal use only" nature of those app registrations. Will update here and in #57403 when it's live.

Cc: @msmimart

[Calvin-Yuhui-Liu]

Now in my understanding the "for internal use only" actually means it's a set of configuration that Identity Experience Framework will use. But I'd suggest you share a diagram of architecture of B2C components. And it'll make everything easier to understand. Thanks.