[BUG] Unable to attach a group to classic modern team site

[gvmadhusudhan]

Notice

Many bugs reported are actually related to the PnP Framework which is used behind the scenes. Consider carefully where to report an issue:

1. Are you using Invoke-PnPSiteTemplate or Get-PnPSiteTemplate? The issue is most likely related to the Provisioning Engine. The Provisioning engine is not located in the PowerShell repo. Please report the issue here: https://github.com/pnp/pnpframework/issues.
2. Is the issue related to the cmdlet itself, its parameters, the syntax, or do you suspect it is the code of the cmdlet that is causing the issue? Then please continue reporting the issue in this repo.
3. If you think that the functionality might be related to the underlying libraries that the cmdlet is calling (We realize that might be difficult to determine), please first double check the code of the cmdlet, which can be found here: https://github.com/pnp/powershell/tree/master/src/Commands. If related to the cmdlet, continue reporting the issue here, otherwise report the issue at https://github.com/pnp/pnpframework/issues

Reporting an Issue or Missing Feature

Issue when attaching a Group to classic sharepoint team site

Expected behavior

Attach a M365 Group to the classic team site

Actual behavior

Get following error when attempting to execute the command
Add-PnPMicrosoft365GroupToSite : An error occurred while processing this request.
At line:1 char:2

• Add-PnPMicrosoft365GroupToSite -Url https://www.avivaworld.com/sites ...

•  + CategoryInfo          : WriteError: (:) [Add-PnPMicrosoft365GroupToSite], ServerException
   + FullyQualifiedErrorId : EXCEPTION,PnP.PowerShell.Commands.Admin.AddMicrosoft365GroupToSite
  
  

Steps to reproduce behavior

Run the command

Add-PnPMicrosoft365GroupToSite -Url "" -Alias "" -DisplayName ""

What is the version of the Cmdlet module you are running?

2.5.0

Which operating system/environment are you running PnP PowerShell on?

• Windows