I have this exact same issue, if anyone figures it out let me know. I've tried every combination of reply URL i could think of.

Hi @ntaylor0909,

You are encountering this issue because the Azure AD application you are using for authentication has not been added as a reply address. You can solve this problem through the Azure management by performing the following

1. Authenticate using credentials that have global admin privileges
2. Click on Azure Active Directory (by default you can find this on the navigation bar on the lower left)
3. Click App registrations
4. Click on the application you created for this deployment
5. Click authentication and add https://yoursite.azurewebsites.net/signin-oidc
6. Click save to commit the changes

I will review the deployment documentation to see if I can identify the root cause for this.

Thank you for the suggestion @IsaiahWilliams however the issue persists :(

Hi @Trafalger1,

Just to confirm did you modify the value of the redirect URI you added to match your deployment? (e.g. if your website is partnersecurescore.azurewebsites.net the address would be https://partnersecurescore.azurewebsites.net/signin-oidc)

Yes i did...

If you'd like i can private email you our web app address @IsaiahWilliams

I have tried about a dozen different URLs with no luck.
@IsaiahWilliams

yes exactly the same....

AADSTS50011: The reply url specified in the request does not match the reply urls configured for the application: '268a2edf-d030-48bd-b74b-xxxxxxxxxxx'.

sends me to this URL when you try and login..

https://login.microsoftonline.com/common/oauth2/authorize?client_id=268a2edf-d030xxxxxxxxxxxxxxxxxx..etc

Sure where would I look to confirm that?

The app ID from the error message and the app ID of the app with the reply URL are identical if thats what your asking.

no joy @IsaiahWilliams

Interesting ...

redirect_uri=http%3A%2F%2Fmyurlapp.azurewebsites.net%2Fsignin-oidc

it worked...the redirect URL needed to be http NOT https:

i am in now i need to set it up for my CSP....

thank you for the help. I wonder why this isn't https tho..but at least for now I can test it out.

Is it possible to force it to https after it's been deployed? or will that require a redeploy?

Thanks for the help. It looks like this was answered in this FAQ as well: https://github.com/Microsoft/Partner-Smart-Office/wiki/FAQ#why-do-i-receive-an-access-denied-message-when-attempting-to-access-the-portal