Org Browser - Need to be Signed in Warning

[DLGross]

I created a new OrgBrowser app, and as soon as it opens in the browser to edit, i get a warning that "The service returned an error: Office365Users!myProfile, You need to be signed in to the services to use this app. " I am signed into Office365. Why am i getting this warning? how can i fix it?

[v-micsh-msft]

Hi Dean Gross,

Could you please share more details about how you add the Office 365 Users connection here?

Please login PowerApps, check the Office 365 connection status, see if it needs to update the credentials.

Adding some reference:

Manage your connections in PowerApps

Regards

[landIT]

Hi, I have the same issue and have signed into the connection?

[modfather83]

Ever get a resolution to this? same issue but i am newbe to powerapps so presuming its me!!

When i edit the app i get the below

[adamm]

Same issue here. Maybe it would not be an issue if I was not using the web version. Anyone get this error in the desktop version?

[Anonymous]

I got same error but I'm already logged. I don't understand why.

[v-micsh-msft]

Hi all,

If you are sitll seeing issues when using the org browser, then please try to remove the Office 365 users conneciton under Data Srouce, then add the Office 365 Users connection again, doing this should clear the error message.

The error message should be caused by the connection not initializing correctly at the begining.

Screenshots for reference.

Regards,

Michael

[Anonymous]

Hi v-micsh-msft 

I am receiving the same error, and I just tested your proposed solution (removing/adding data source) but it did not resolve the error for me.

Regards,

Daniela

[Anonymous]

I also reviewed this post which proposed a solution (add "If(!IsBlank" to any formula showing an error) but this did not work for me.

The error seems to be related to the 'DirectReports' and 'userId', however strangely the only error triangle I get in the app itself is regarding the work phone number (which was a workaround found here😞

This is a great sample app which we aim to roll out across the organization, but we cannot do it as long as this error would appear for every user upon launching the app.. it would be great to find a solution for this. 🙂

[Anonymous]

(Posted previous message twice)