Feb 21 2018 11:17 AM
Hasn't it been in Preview for ages now? Or was that Private? :)
Feb 21 2018 12:48 PM
Any idea why I'm getting the following error when I try the sample code ? i have AzureADPreview 2.0.0.154 installed
$Setting = Get-AzureADDirectorySetting -Id (Get-AzureADDirectorySetting | where -Property DisplayName -Value "Group.Unified" -EQ).id
Get-AzureADDirectorySetting : Cannot bind argument to parameter 'Id' because it is null.
At line:1 char:44
+ ... Setting -Id (Get-AzureADDirectorySetting | where -Property DisplayNam ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidData: (:) [Get-AzureADDirectorySetting], ParameterBindingValidationException
+ FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.Open.MSGraphBeta.PowerShell.GetDirectorySetting
Feb 22 2018 12:52 AM
@Dean Gross, your sample works fine for me. I guess you can simply run it like this instead:
Get-AzureADDirectorySetting | ? {$_.DisplayName -eq "Group.Unified"}
Feb 22 2018 10:10 AM
Thanks, I tried yours and i'm not getting an error, but as you can see, I'm not getting any results.
PS C:\Scripts> $setting= Get-AzureADDirectorySetting | ? {$_.DisplayName -eq "Group.Unified"}
PS C:\Scripts> $setting.values
PS C:\Scripts>
Feb 22 2018 10:10 AM - edited Feb 22 2018 10:12 AM
You're connected to Azure AD - right? It could be that the quotation marks surrounding Group.Unified are printer's quotations rather than the straight quotation marks required by PowerShell. That often happens when you cut and paste commands from articles.
What does running the command below show? You can see my complete policy...
PS C:\temp> Get-AzureAdDirectorySetting | ForEach Values Name Value ---- ----- CustomBlockedWordsList Sexy,Stupid,Giggles,Funny,CFO,CEO,**bleep**,Payroll,Supercalifragilisticexpialidocious,Silly EnableMSStandardBlockedWords false ClassificationDescriptions General Use:Anyone can access,External Access:Available outside the company,Internal Only:Must not b... DefaultClassification Confidential PrefixSuffixNamingRequirement O365Grp-[GroupName] AllowGuestsToBeGroupOwner False AllowGuestsToAccessGroups True GuestUsageGuidelinesUrl Http://office365itpros.com/GuestUserGuidelines.html GroupCreationAllowedGroupId 12cb915b-2365-4bed-baf6-6257b3543273 AllowToAddGuests True UsageGuidelinesUrl Http://office365exchange.com/GroupGuidelines.html ClassificationList General Use,External Access,Internal Only,Confidential EnableGroupCreation False
I
Feb 22 2018 10:14 AM
It's now public, but I thought it was pretty public when Microsoft revealed the policy at Ignite 2016 (announcement) and then discussed its operation in depth at Ignite 2017. What has changed is that Microsoft call this an AAD naming policy now... maybe to help justify the need for AAD premium licenses.
Feb 22 2018 10:28 AM
Feb 22 2018 10:31 AM
Did you ever create an Azure AD policy object to store custom settings for the domain? From Chapter 15 of "Office 365 for IT Pros":
[PS] C:\> $Policy = Get-AzureADDirectorySettingTemplate | ? {$_.DisplayName -eq "Group.Unified"} [PS] C:\> $Settings = $Policy.CreateDirectorySetting() [PS] C:\> New-AzureADDirectorySetting -DirectorySetting $Settings
I made the assumption that you already had a policy...
Feb 22 2018 10:50 AM
Feb 22 2018 11:10 AM
This is why I have a book and why I update it all the time. It's impossible to keep track of all the bits and pieces that happen inside Office 365 and the devil is in the detail, so I write it down so that I can get back to it when I need...
Feb 22 2018 11:50 AM
I think i need to just keep your book open in my pdf reader and only close it to get the updates. There is so much good content in it that I need to get more familiar with.
Feb 22 2018 12:43 PM
I need to keep the book open all the time to remember what's written in it...
Mar 07 2018 02:46 PM
is there a time delay on a change like this? I've confirmed these settings are in place (almost 6 hours ago), and they don't seem to be enforced yet.
Apr 20 2018 04:08 AM
Hi!
We would like to implement a naming policy that adds custom attribute number 14 from Azure AD as a prefix. Is that possible? What is the syntax for fetching that custom attribute?
Would you say it is safe to add the naming policy in a production environment even though it is still in Public Beta and not GA?
Apr 20 2018 06:28 AM
AFAIK, the Azure AD naming policy doesn't take a custom attribute into account when it constructs names. This would be easy to do with PowerShell by updating the DisplayName attribute with whatever's in CustomAttribute14 after a group exists.
Apr 20 2018 06:29 AM
And it is safe to use the policy. All it's doing is making sure that the DisplayName attribute is correctly populated. You can do that yourself or let the policy do it.