Forum Discussion
Error: AADSTS50076 - AcquireTokenAsync fails with multi-factor auth
- Anonymous8 years ago
I don't think MFA is supported. This is more of an Azure AD area which is a little outside of my area of expertise, but you can create a policy which enforces MFA amongh other things. In this case you'd want to choose not to add a policy in Azure AD so that MFA isn't required for this user.
- 8 years ago
Hi Anonymous,
I guess your scenario is App owns data. I'm afraid the MFA isn't supported. It's obvious we can't ask our customers to finish the multi-factor auth for the sole account. The authentication should be quiet in the background.
Please also refer to Developer/Error-AADSTS50076-while-trying-to-login-on-App-owns-data-sample
Best Regards,
Dale
Hi Anonymous,
I guess your scenario is App owns data. I'm afraid the MFA isn't supported. It's obvious we can't ask our customers to finish the multi-factor auth for the sole account. The authentication should be quiet in the background.
Please also refer to Developer/Error-AADSTS50076-while-trying-to-login-on-App-owns-data-sample
Best Regards,
Dale
Hi v-jiascu-msft, I agree that the authentication should happen quietly in the background. For MFA scenarios creating an app password (similar to app passwords for office365) for the registered app could do the job.
We'll find a workaround as long as MFA scenarios are not supported.
Kind regards,
NAJ