<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Error: AADSTS50076 - AcquireTokenAsync fails with multi-factor auth in Developer</title>
    <link>https://community.fabric.microsoft.com/t5/Developer/Error-AADSTS50076-AcquireTokenAsync-fails-with-multi-factor-auth/m-p/443605#M13676</link>
    <description>&lt;P&gt;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.&lt;/P&gt;</description>
    <pubDate>Tue, 19 Jun 2018 19:59:23 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2018-06-19T19:59:23Z</dc:date>
    <item>
      <title>Error: AADSTS50076 - AcquireTokenAsync fails with multi-factor auth</title>
      <link>https://community.fabric.microsoft.com/t5/Developer/Error-AADSTS50076-AcquireTokenAsync-fails-with-multi-factor-auth/m-p/443510#M13674</link>
      <description>&lt;P&gt;Hi, is&amp;nbsp;there any way for power bi embedded of acquiring token using a multi-factor auth pro user? Or would one have to tend to creating a new tenant for power bi or creating a non-MFA "service user"?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We're currently receiving below error&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;I&gt;AADSTS50076: Due to a configuration change made by your administrator, or because you moved to a new location, you must use multi-factor authentication to access&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/I&gt;&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 19 Jun 2018 18:31:30 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Developer/Error-AADSTS50076-AcquireTokenAsync-fails-with-multi-factor-auth/m-p/443510#M13674</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2018-06-19T18:31:30Z</dc:date>
    </item>
    <item>
      <title>Re: Error: AADSTS50076 - AcquireTokenAsync fails with multi-factor auth</title>
      <link>https://community.fabric.microsoft.com/t5/Developer/Error-AADSTS50076-AcquireTokenAsync-fails-with-multi-factor-auth/m-p/443605#M13676</link>
      <description>&lt;P&gt;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.&lt;/P&gt;</description>
      <pubDate>Tue, 19 Jun 2018 19:59:23 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Developer/Error-AADSTS50076-AcquireTokenAsync-fails-with-multi-factor-auth/m-p/443605#M13676</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2018-06-19T19:59:23Z</dc:date>
    </item>
    <item>
      <title>Re: Error: AADSTS50076 - AcquireTokenAsync fails with multi-factor auth</title>
      <link>https://community.fabric.microsoft.com/t5/Developer/Error-AADSTS50076-AcquireTokenAsync-fails-with-multi-factor-auth/m-p/444664#M13707</link>
      <description>&lt;P&gt;Hi&amp;nbsp;@Anonymous&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;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.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please also refer to&amp;nbsp;&lt;A href="https://community.powerbi.com/t5/Developer/Error-AADSTS50076-while-trying-to-login-on-App-owns-data-sample/td-p/257339" target="_self"&gt;Developer/Error-AADSTS50076-while-trying-to-login-on-App-owns-data-sample&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P style="margin: 0in; font-family: 'Segoe UI'; font-size: 10.5pt; color: #333333;"&gt;Best Regards,&lt;/P&gt;
&lt;P style="margin: 0in; font-family: 'Segoe UI'; font-size: 10.5pt; color: #333333;"&gt;Dale&lt;/P&gt;</description>
      <pubDate>Thu, 21 Jun 2018 02:38:44 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Developer/Error-AADSTS50076-AcquireTokenAsync-fails-with-multi-factor-auth/m-p/444664#M13707</guid>
      <dc:creator>v-jiascu-msft</dc:creator>
      <dc:date>2018-06-21T02:38:44Z</dc:date>
    </item>
    <item>
      <title>Re: Error: AADSTS50076 - AcquireTokenAsync fails with multi-factor auth</title>
      <link>https://community.fabric.microsoft.com/t5/Developer/Error-AADSTS50076-AcquireTokenAsync-fails-with-multi-factor-auth/m-p/444956#M13717</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.fabric.microsoft.com/t5/user/viewprofilepage/user-id/28904"&gt;@v-jiascu-msft&lt;/a&gt;, I agree that the authentication should&amp;nbsp;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.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.microsoft.com/en-us/azure/multi-factor-authentication/end-user/multi-factor-authentication-end-user-app-passwords" target="_blank"&gt;https://docs.microsoft.com/en-us/azure/multi-factor-authentication/end-user/multi-factor-authentication-end-user-app-passwords&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We'll&amp;nbsp;find a workaround as long as MFA scenarios are not supported.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;NAJ&lt;/P&gt;</description>
      <pubDate>Thu, 21 Jun 2018 08:49:49 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Developer/Error-AADSTS50076-AcquireTokenAsync-fails-with-multi-factor-auth/m-p/444956#M13717</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2018-06-21T08:49:49Z</dc:date>
    </item>
  </channel>
</rss>

