Frederick Lin
My feedback
-
61 votes
-
7 votesFrederick Lin
shared this idea
·
-
145 votesFrederick Lin
supported this idea
·
-
24 votesFrederick Lin
shared this idea
·
-
25 votesFrederick Lin
commented
My mistake, it is 300 characters. The error message when you try to set this in Powershell is:
Set-AzureADDirectorySetting : Error occurred while executing SetDirectorySetting
Code: Request_BadRequest
Message: Property ClassificationDescriptions is invalid.
InnerError:
RequestId: GUID
DateTimeStamp: Fri, 05 Jan 2018 18:36:14 GMT
HttpStatusCode: BadRequest
HttpStatusDescription: Bad Request
HttpResponseStatus: Completed
At line:1 char:1
+ Set-AzureADDirectorySetting -id GUID ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Set-AzureADDirectorySetting], ApiException
+ FullyQualifiedErrorId : Microsoft.Open.MSGraphBeta.Client.ApiException,Microsoft.Open.MSGraphBeta.PowerShell.SetDirectorySettingFrederick Lin
shared this idea
·
-
1,604 votes
To change the email address of the group, follow the best answer here: https://answers.microsoft.com/en-us/msoffice/forum/msoffice_o365admin-mso_exchon-mso_o365b/how-to-add-an-email-alias-to-an-o365-group/79d94383-442a-4e3a-ac62-4ff1ea8af962.
We’re working on renaming the Team Site. Stay tuned.
Frederick Lin
commented
This gets alot more complicated if there is a naming policy which by Microsoft's implementation is based user attributes associated with the *person that is creating the Office 365 Group*. When an administrator modifies the group, those attributes could be different, especially for Groups that have a naming policy configured that reflect on attributes such as the user's business unit, location, or department. To address this, we implemented our own naming policy but it isn't perfect; the naming is done after the fact and not immediately after a change. Would be nice to have a webhook into this sort of event to link this into an Azure web job for example.
Then there are things that cannot be renamed at all such as the site collection URL.
-
17 votesFrederick Lin
supported this idea
·
-
171 votesFrederick Lin
supported this idea
·
-
203 votes
We are providing the ability that will sync changes in email addresses of groups between EXO and AAD
Roadmap item: https://products.office.com/en-US/business/office-365-roadmap?filters=&freeformsearch=27891&featureid=27891Frederick Lin
commented
Frederick Lin
commented
I also just want to add that this is something that we found to be an issue for a tenant-to-tenant migration. A domain cannot be removed from an O365 tenant with objects having references to the domain required for removal. Which would mean needing to delete O365 Groups and all of the underlying services BEFORE migration. Manageable if you have a handful of Groups to migrate. A nightmare if you have much more.
Frederick Lin
shared this idea
·
-
82 votes
Good news!
We’re currently working on adding naming policy into Office 365 Groups.
You can follow this in our roadmap here:
https://fasttrack.microsoft.com/roadmap?filters=#I-31839Frederick Lin
commented
Also it would be nice to have naming policy options configurable for display name, email address, and custom attributes (Unified group properties). Prefix/Suffixes should be configurable with a separator text. For example:
Display Name: Super Secret
Email Address: ogrp-supersecret@contoso.com
Custom Attribute 1: Finance
Custom Attribute 2: ContosoDisplay Name: Northwind
Email Address: ogrp-northwind@adventureworks.com
Custom Attribute 1: Finance
Custom Attribute 2: Adventureworks -
1,592 votesFrederick Lin
commented
We've reconfigured or tenant to have Groups be created in the /teams managed path but it doesn't help with Groups that already reside in the /sites managed path.
Frederick Lin
supported this idea
·
-
77 votesFrederick Lin
supported this idea
·
Also want to add that the group's Object ID is reflected accurately when viewing this through the Azure Portal.