A cloud-based identity and access management service for securing user authentication and resource access
If either Object ID is still a soft-deleted group, restore that group first because restoration retains its original Object ID, memberships, and application assignments and may make the existing Power Apps permission resolve again.^1^
1. Check whether the original groups can be restored
- Open Microsoft Entra admin center → Entra ID → Groups → Deleted groups.
- Search for each old Object ID.
- If found, record its display name, deletion date, group type, and membership.
- Review the membership before restoring. Restoration can re-enable historical access for previous members.
- Select the group and choose Restore.
- Return to Power Apps → Apps → select the app → Share → Manage access and check whether the assignment now resolves to the restored group.
Microsoft 365 groups and cloud security groups remain soft-deleted for 30 days. During that period, important properties—including Object ID, memberships, and application assignments—are maintained. Hard-deleted objects cannot be restored.^1^
An administrator can also query a particular deleted Object ID through Microsoft Graph:
GET https://graph.microsoft.com/v1.0/directory/deletedItems/{object-id}
Authorization: Bearer {token}
Accept: application/json
A successful lookup returns 200 OK. For a deleted group, groupTypes: [] identifies a security group; do not rely on securityEnabled, because it has a known limitation for soft-deleted security groups.^2^
This recovery path applies only where the group entered a supported soft-deleted state. A synchronized group’s deletion might not be recoverable this way, depending on how it was removed and the tenant scenario.
2. If the old group is not recoverable
There is no documented customer-accessible, guaranteed old-Object-ID-to-new-Object-ID mapping when a group was deleted and recreated. The replacement is a separate Entra object, so Power Apps continues to hold the original principal ID in its role assignment.
Correlate the objects using retained evidence:
- Entra audit logs: Open Entra ID → Monitoring & health → Audit logs. Search the migration period and filter for Delete group, Hard Delete group, and Add group. Inspect each event’s target resources for the stale Object ID. Audit logs record deletion events, but they do not inherently establish which newly created group replaced the deleted group.^1^
- Archived audit/SIEM data: Check Microsoft Sentinel, Log Analytics, or another archive if Entra’s interactive retention period has expired. Microsoft recommends exporting audit logs for longer retention.^3^
- Migration records: Compare display name, membership, mail/proxy addresses, source OU, and migration timestamps.
- On-premises SID: For groups synchronized from AD, Microsoft Graph exposes the read-only
onPremisesSecurityIdentifier. If both historical and current records contain the same SID, that provides a stronger correlation than display name alone.^4^ - Entra Connect evidence: Retained connector-space entries, export history, synchronization logs, or migration reports might help. Synchronization history is not a guaranteed permanent mapping store.
For future group migrations, Group Source of Authority conversion can convert an eligible synchronized group into a cloud-managed object rather than recreating it. This lets Entra Connect stop synchronizing that same group object and reduces identity-breaking replacements.^5^
3. Replace the stale Power Apps permission
After identifying the correct current group:
- Open Power Apps → Apps → select the app → Share → Manage access.
- Remove the unresolved old assignment.
- Enter the current Entra security group name and assign the required User or Co-owner permission.
- If Dataverse is used, assign the appropriate Dataverse security role as well.
- Save, publish, and test with a member of the replacement group.
Power Apps sharing resolves users and security groups from Microsoft Entra ID. App sharing does not automatically grant access to dependent SharePoint sites, flows, gateways, connections, or other data sources; update those permissions separately.^6^
If the UI cannot remove an unresolved principal, use the supported Power Apps administration cmdlets to obtain its role ID and delete that assignment:
Add-PowerAppsAccount
$roles = Get-AdminPowerAppRoleAssignment `
-EnvironmentName "<environment-id>" -AppName "<app-id>"
$roles | Format-List *
Remove-AdminPowerAppRoleAssignment `
-EnvironmentName "<environment-id>" `
-AppName "<app-id>" -RoleId "<stale-role-id>"
These cmdlets support reading and deleting canvas-app permissions; removal requires the environment ID, app ID, and assignment’s role ID.^7^^8^
4. Escalation when tenant evidence is exhausted
Open a Microsoft support request through the Power Platform admin center or Microsoft 365 admin center and provide:
- Tenant, environment, and app IDs
- Both unresolved group Object IDs
- Approximate migration/deletion dates
- App role-assignment output
- Entra audit and synchronization logs
- Suspected replacement groups and their Object IDs/SIDs
Support can investigate tenant-specific service information that remains available, but recovery or an authoritative mapping cannot be guaranteed after the original objects and relevant logs have expired.
References
- Recover from deletions
- Get deleted item (directory object)
- Recoverability best practices
- group resource type
- Embrace cloud-first posture: Convert Group Source of Authority to the cloud
- Share a canvas app with your organization
- PowerShell support for Power Apps and Power Automate
- Remove-AdminPowerAppRoleAssignment-Syntax