Access denied Get/Set-PnPUnifiedGroup after running Add-PnPOffice365GroupToSite

[markgort86]

@VesaJuvonen In our organisation we're having some troubles with Set/Get-PnPUnifiedGroup after connecting a SharePoint site to an Microsoft 365 group. I created a github issue on PnP-PowerShell (see link below). But nobody is responding to it. The proces to reproduce is the following:

• Connect-SPOService
• Add-PnPOffice365GroupToSite or Set-SPOSiteOffice365Group (last one is not supported for a Production environment)
• Connect-PnPOnline (appid and appsecret)
• Get-PnPUnifiedGroup - identity [GroupID]

Result of the last command-let is an access denied visible in Fiddler (only on two tenants where Exhange Online is not fully configured). On a tenant where Exchange Online is configured this process is working fine. We are using Set-PnPUnifiedGroup to set the members and owners to this newly created Microsoft 365 group. Not the AzureAD commands that is visible in the script on this documentation page. If i'm using Get-UnifiedGroup (Exchange Online Module) i don't get a access denied, but this one is not using our App Registration. I hope you can give me some details what is going wrong over here.

See for more details: pnp/PnP-PowerShell#2842

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: bb7f9871-ee80-3bed-5085-fd7e2374641d
• Version Independent ID: fe06b607-6f98-edcb-f6ff-f0fa426d5666
• Content: Connect to a Microsoft 365 group
• Content Source: docs/transform/modernize-connect-to-office365-group.md
• Product: sharepoint
• GitHub Login: @spdevdocs
• Microsoft Alias: spdevdocs

[msft-github-bot]

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

[github-actions]

Thank you for taking the time to file an issue. We periodically archive older or inactive issues as part of our issue management process, which automatically closes them once they are archived.

If you’d like to understand more about why and how we handle archived (closed) issues, please see Our approach to closed issues.

We appreciate your contribution and if this is still an active issue with the latest SPFx versions, please do resubmit the details. We needed to perform a cleanup, so that we can start with a clean table with a new process. We apologize for the inconvenience this might cause.