This Bug is here to raise attention on the fact that creationOptions in graph-API Post /groups is ignored since about last week of May.
While Microsoft claims that this was never officially documented, it's also the only way to create a Group-Site whit an other Language then the Base-Language of your SharePoint Root-Site or to create a Group where the Group-Alias should be different from the Url.
Why Base Language matters - it defines the Url of your default Library and the Language in which you get notifications - just to mention 2 reasons.
Please Comment on this Bug if you are affected as well in the hope to raise enough attention to make them reconsider or provide an official supported way.
In the current situation you can
- Fallback to the undocumented API on SharePoint which still offers the Parameters and is used by the SharePoint UI.
Drawback: It's not documented either and it works with user context only which means you can create 250 Groups before you get the Error Microsoft.Online.DirectoryServices.DirectoryQuotaExceededException if your User is not at least in the Role "Group Managers"
- The other possibility is to create a SharePoint Site from STS#3 Template with the correct settings, then Groupify and the Teamify if needed...
Before mid May this would have been working and thats what UnifiedGroupsUtility in pnpframework would do if you specify the Language.
{
"displayName": "Test-Remove4u",
"description": "Test-Remove4u-Desc",
"groupTypes": [
"Unified"
],
"mailEnabled": true,
"mailNickname": "Remove4u",
"securityEnabled": true,
"visibility": "Private",
"owners@odata.bind": [
"https://graph.microsoft.com/v1.0/users/ba7976ed-3011-4b54-8f97-xxxxxxxxxxxx"
],
"members@odata.bind": [
"https://graph.microsoft.com/v1.0/users/ba7976ed-3011-4b54-8f97-xxxxxxxxxxxx"
],
"classification": null,
"resourceProvisioningOptions": [],
"resourceBehaviorOptions": [
"WelcomeEmailDisabled",
"ProvisionGroupHomepage"
],
"creationOptions": [
"SPSiteLanguage:1031",
"SiteAlias:Test-Remove4u",
"SharePointReadOnlyMembers"
]
}
Just to be complete - the v1.0 API does accept the creationOptions but ignores the settings and the beta endpoint returns Bad Request as soon as you add creationOptions.
Limit of Groups
@jansenbe @VesaJuvonen @erwinvanhunen
This Bug is here to raise attention on the fact that creationOptions in graph-API Post /groups is ignored since about last week of May.
While Microsoft claims that this was never officially documented, it's also the only way to create a Group-Site whit an other Language then the Base-Language of your SharePoint Root-Site or to create a Group where the Group-Alias should be different from the Url.
Why Base Language matters - it defines the Url of your default Library and the Language in which you get notifications - just to mention 2 reasons.
Please Comment on this Bug if you are affected as well in the hope to raise enough attention to make them reconsider or provide an official supported way.
In the current situation you can
Drawback: It's not documented either and it works with user context only which means you can create 250 Groups before you get the Error Microsoft.Online.DirectoryServices.DirectoryQuotaExceededException if your User is not at least in the Role "Group Managers"
Before mid May this would have been working and thats what UnifiedGroupsUtility in pnpframework would do if you specify the Language.
Just to be complete - the v1.0 API does accept the creationOptions but ignores the settings and the beta endpoint returns Bad Request as soon as you add creationOptions.
Limit of Groups
@jansenbe @VesaJuvonen @erwinvanhunen