Answered

Error when sharing the power app

(0) Share

Report

Posted on by GB-05080356-0

This error appears when I try to share my power app with everyone in my organization. I searched for everyone in the input box and the group "Everyone in [our domain]" appears. When I select it and try to share the error "Principle object is null" appears and the app is not shared. How can I solve this?

Categories:

Building Power Apps

I have the same question (0)

All responses (6)

Answers (1)

Sort by

Bezanca 686 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hey GB-05080356-0

Do you have Power Platform admin access on the account that you're trying to share the app with 'everyone'?

The ability to share an app with 'everyone' was recently locked down by Microsoft.
The Share with Everyone feature is disabled by default in Power Platform. We recommend you keep this setting disabled to limit the overexposure of canvas apps with unintended users. The Everyone group for your organization contains all users who have ever logged in to your tenant, which includes guests and internal members. It doesn't only include internal employees within your tenant. Additionally, the membership of the Everyone group can't be edited nor viewed. Learn more about special identity groups.

If you want to share with all internal employees or a large group of people, consider using an existing security group or creating a security group to share your app.

When Share with Everyone is turned off, only Dynamics 365 administrators, Power Platform administrators, and global administrators can share an application with everyone in the environment

Details can be found here -

https://learn.microsoft.com/en-us/power-platform/guidance/adoption/secure-default-environment#limit-sharing-with-everyone

--

Note: If this has solved your query then please mark this as a verified answer. Thank you!

Was this reply helpful? Yes No
bscarlavai33 756 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Have you tried sharing to a single user? Does that work?

Was this reply helpful? Yes No
GB-05080356-0 20 on at

Like (0)

Report
Copy link

Link copied!

Dear bscarlavai33 & Bezanca,

Thank you for your responses. I was able to successfully share the app with an individual user. I also granted co-owner access to a global admin account and attempted to share the app from that account, but the error "Primary object is null" still appears when trying to share it with everyone.

Was this reply helpful? Yes No
Suggested answer

Pol Escolano 10 on at

Like (0)

Report
Copy link

Link copied!

Hi, it looks like an IT problem, ask your IT admins team to create a group of users with all the users you need to access in the app, then this same group need to be able to access to the enviroment your solution(app) is created. Hope it helps :)

Was this reply helpful? Yes No
Suggested answer

Bezanca 686 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hey @GB-05080356-0,

It might be worth checking whether the ‘everyone’ group is disabled in your tenant. Here’s a good guide on checking but you’ll need to find someone with the right permissions to do so -

https://www.sharepointdiary.com/2017/11/sharepoint-online-enable-disable-everyone-group-using-powershell.html

Here is also some good info from Microsoft on limiting oversharing of Apps -

https://learn.microsoft.com/en-us/power-platform/guidance/adoption/secure-default-environment#limit-sharing-with-everyone

I agree with @Pol Escolano that in many cases a better way to manage Apps is creating a separate AD group and managing that with your normal AD access request process.

Thanks!

Was this reply helpful? Yes No
Verified answer

GB-05080356-0 20 on at

Like (0)

Report
Copy link

Link copied!

Dear Bezanca, Pol Escolano, bscarlavai33,

Thanks to everyone who pitched in! I found a working solution to my issue.

I created a Dynamic Security Group in the Microsoft Entra admin center and shared my Power App with that group. This approach automatically includes all internal users based on a dynamic rule, so I no longer need to manage access manually.

Creating the dynamic group solved the problem by ensuring that only internal users are added automatically.

For anyone facing a similar situation, here's the official Microsoft guide on how to create such a group:

🔗 Creating a group of members only (Microsoft Docs)

Hope this helps others too. Thanks again!

Was this reply helpful? Yes No