Forum Discussion
Enforce naming conventions across Office 365 Groups
- DeletedMar 12, 2018
I ran into that too, and I think my problem was because I hadn't actually created the Group.Unified object/setting in AzureAD yet. Therefore, the error report was technically correct.
Check this to see if you have anything configured:
Get-AzureADDirectorySetting | ForEach Values
If not, create the settings AAD object:
Creating the Group.Unified Settings object (1-time task)
$template = Get-AzureADDirectorySettingTemplate | where-object {$_.displayname -eq “Group.Unified”}
$setting = $template.CreateDirectorySetting()
New-AzureADDirectorySetting -DirectorySetting $setting
After that, the 'is null' error should go away as the setting actually exists.
Re-run Get-AzureADDirectorySetting | ForEach Values and you should at least see the blank settings.
I found this site extremely helpful getting my settings configured & managing them:
https://drewmadelung.com/managing-office-365-group-using-azure-ad-powershell-v2/
HTH
I had a lot of success configuring and using the Groups AAD settings last week, with one exception: Naming Policy. Below is the output from the Groups Settings I have in place.
I cannot get the "O365Grp-[GroupName]" prefix to be generated on any new groups. Based on the research I did, the brackets serve to insert the actual group name, and it's just not happening. When I created the 'PrefixSuffixNamingRequirement' setting, I didn't get an error. I've also changed it around a bit, to include/exclude the [GroupName] component but nothing made any difference.
Any suggestions are appreciated.
Thx
Any suggestions?