Access, security and governance

Copy link

ms auth status
ms app share alice@contoso.com,bob@contoso.com --access play
ms app share dev-team@contoso.com --access edit
ms app share list --access play
ms app share list --access edit
ms app unshare alice@contoso.com --access play
ms app share link create
ms app share link list --json
ms app share link revoke --link-id <id>
ms app list --permission play

• Principals are a comma-separated list of email addresses or Entra object ids. Unresolved addresses produce warnings while the rest go through, so read the output rather than assuming everyone was added. D
• share list needs --access; run it for both levels. The flag is --access; there is no --role. D
• An organization link is revocable and scoped to your tenant, never anonymous. Redeeming it grants Microsoft App Reader, and revoking it removes the role from everyone who redeemed it. D

Copy link

• They can open the link you send, or find every app shared with them at managedapps.cloud.microsoft. D
• On first open they sign in and, for apps that use connectors, see a connection consent dialog listing the sources and actions. Single sign-on is attempted, and they can sign in manually to repair a failed connection. D
• If their environment, license or data permissions are missing, the app opens but fails at the first data call, or is blocked after 20 app operations or five minutes. Always test with an ordinary colleague's account, never only your own. DI
• For Teams, Microsoft's documented route is posting the link in a channel. Pinning a managed app as a Teams tab is not documented, and the content security policy's frame-ancestors rule controls where an app may be embedded. D
• Whether recipients get an automatic email is not documented for Cowork or the CLI, so send the link yourself with a line on what the app is for. DI

Copy link

• Share with groups, not lists of people. Entra security groups and Microsoft 365 groups are supported. Distribution lists are not documented, so use a security group's object id when in doubt. D
• One group for all four checks. Use the same group to share the app, grant the SharePoint or Dataverse permissions and assign the license or spending policy; joiners and leavers then change in one place. I
• Environment security group. If an admin restricts the environment to a security group (Power Platform admin center, Manage, Environments, the environment, Edit, Security group), a person needs that membership and the app share; sharing doesn't bypass the group, and joining the group doesn't share any app. D
• Organization rules. Admins set organization-wide and guest sharing for managed apps under Microsoft 365 admin center, Apps, Settings, Environment groups, the group, Sharing; these rules are separate from general Power Platform sharing settings. D
• Inventory. Admins see every app under Apps, All apps (details, usage, monitoring, data and tools), can block an app (access stops, app and data kept) or delete it, and see changes within about 15 minutes. Numeric sharing caps are not documented. D

Copy link

• Edit access is repository collaboration, not co-ownership. No ownership transfer or co-owner procedure is documented yet, so make a named backup owner an editor from day one and record both names in README.md. DI

Copy link

Decide this in the setup → Step 3: People and devices

Copy link

• Remove play and edit separately; no single operation removes both. D
• Revoke organization links you no longer need, then list grants again to confirm. D
• Remove the person from the data source's group too; app access and data access end independently. I
• Keep the share inventories from ms app share list --access play and --access edit with each release record, since a published audit-event catalog for app sharing doesn't exist yet. DI

Copy link

• The live version is the one you tested, and publishing and sharing are treated as separate steps. D
• Play and edit inventories are reviewed; link ids and warnings are saved. D
• The environment's security group, sharing rules, data permissions and runtime coverage all include the audience. D
• One ordinary user, one read-only user and one person with no data access have tried the published app. I
• The backup owner, support contact, budget owner and revocation steps are written in README.md. I

Copy link

Part 15 walks through sharing step by step; this section is the security view of the same controls.

• Apps are private until shared. You can share with people or groups, including Entra security groups, or with a "People in your organization" link; revoking a link removes access for everyone who used it. D
• If the environment has a security group, it still applies: sharing does not bypass it, and joining the group grants nothing by itself. D

From a security view, check 2 matters most: give edit only to co-owners, because the sharing tool observed in Code grants a repository contributor role, which also unlocks the preview. DO

Partner-facing managed apps are not possible today, so pick one of these alternatives instead.

Copy link

By default each person runs the app on their own connection and sees only what their permissions allow, after approving the connection the first time. D An app can instead use a shared connection with a service identity, but shared references must declare their allowed actions or packaging and deployment fail, the CLI can create a shared reference without asking when a connector's sign-in type is shareable, and a shared table read does not restrict which rows each person sees. Check ms.config.json after every binding. DC

Anything the app downloads is visible to the person using it, because browser tools show request and response payloads. Hiding a column in the interface is not security; enforce row and column rules at the source. D

The documentation disagrees with itself here. Cowork's page warns that anyone with the link can open the app "including its data"; the Copilot Code and Studio pages say sharing never grants data access. Both can be true, depending on whether the app uses per-user or shared connections. Test with a non-owner account before you share widely. DI

Copy link

A production partner-sales app adds its own guardrails on top of the platform's. O

• Send checks on every path that sends or saves anything outside the app, with a test that fails if any path bypasses them.
• Recipient guards that warn on unknown domains and block contacts the source system marks as off-limits.
• Read-only adapters for systems the team doesn't own, with a test that fails on any write call.
• An identity check: if a sender can't be matched to a known organization, no data is attributed to that organization.
• Plain-text rendering, or sanitizing, of anything that came from mail, files, Copilot or the web.
• A kill switch, planned as team-shared configuration, to turn a feature off without a release.

Copy link

If your tenant already uses advanced connector policies and classic DLP, the most restrictive result wins, and the admin center can show "no connectors allowed" for an older environment group even while classic DLP is what actually governs it. D

Copy link

• The inventory under Apps, All apps lists owner (which can differ from the creator), status, hosting region and environment group, with tabs for details, usage, monitoring and data and tools; it exports to CSV and refreshes within 15 minutes. Admins can block an app, which keeps the app and its data, or delete it permanently. D
• Monitoring shows app-open success, time to interactive at the 75th percentile, sessions, data-request success and latency, aggregated hourly or daily and kept 28 days, with up to five alert rules per tenant. D
• Admins cannot see exact destinations, the actions an app ran or each user's data permissions, and no managed-app events are documented in the Purview audit log yet; one community report found none after 24 hours. Code's own actions are audited: code generated, commands run and files read or written. DC

Copy link

• Taking full control freezes the defaults. When an admin takes full control of an environment group's connector policy, Microsoft's automatic updates to that policy stop, so new first-party connectors no longer appear on their own. D
• Group rules lock environment settings. A published environment-group rule supersedes and locks the matching environment setting, and per-environment exceptions aren't supported. Ask for changes at the group level. D
• Personal developer environments are Managed Environments without Dataverse at first. Routing is always on; makers who match no routing rule can be blocked from creating apps until an admin adds one. D
• CLI creation and external artifacts are separate switches. CLI app creation lives under Power Platform admin center, Copilot, Settings, Managed apps; uploading externally built artifacts has its own setting. D
• Billing has two halves. Building is billed through each tool (Cowork's spending policy, Code's Copilot credits, the environment for Copilot Studio); running is covered by Power Apps Premium or a spending policy for managed apps under Microsoft 365 admin center, Copilot, Cost management. Work IQ calls are billed separately. D

Copy link

Copy link