Hello, @hampton123 - I followed the steps in the doc and was able to implement the solution without encountering any issues. The only minor discrepancy that I identified in the doc was at step 7 of the Configure the JavaScript SPA for Azure AD B2C section. Although the doc communicates the correct format for the Authority value as https://{b2ctenantname}.b2clogin.com/tfp/{b2ctenantname}.onmicrosoft.com}/{signupandsigninpolicyname}
, it provides an incorrect example for the {signupandsigninpolicyname}
portion as Frontendapp_signupandsignin
but it should really be prefixed with B2C_1_
as follows: B2C_1_Frontendapp_signupandsignin
Oh, another one that I did differently than in the doc was the value for the backend
field in the msal
config. The sample in the doc has it as follows:
backend: "{APIBASEURL}/hello" // The location that we'll call for the backend api, this should be hosted in API Management, suffixed with the name of the API operation (in the sample this is '/hello').
But in my case, since the API on the Function App maps to APIM as follows, I needed to change it as such:
backend: "https://<apim-instance-name>.azure-api.net/<functionapp-name>/HttpTrigger" // The location that we'll call for the backend api, this should be hosted in API Management, suffixed with the name of the API operation (in the sample this is '/hello').
I will work internally with our content team to address the issue above.
Overall, I think the config steps for both backend and frontend app registrations need to be followed very thoroughly and carefully verified against the doc while you capture/record values and complete them, otherwise, it seemed like they were quite prone to a mistake.
I'm not entirely sure if the discrepancies above were the root cause of the problem you've been hitting but if they don't resolve the issue, I'd be happy to help in a 1:1 setting if need be & review your setup ;)