Feedback by UserVoice

Frederick Lin

My feedback

  1. 70 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Microsoft 365 Groups  ·  Flag idea as inappropriate…  ·  Admin →
  2. 7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Microsoft 365 Groups  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Frederick Lin commented  · 

    Also want to add that the group's Object ID is reflected accurately when viewing this through the Azure Portal.

    Frederick Lin shared this idea  · 
  3. 179 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Frederick Lin supported this idea  · 
  4. 30 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Microsoft 365 Groups  ·  Flag idea as inappropriate…  ·  Admin →
    Frederick Lin shared this idea  · 
  5. 23 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Microsoft 365 Groups  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Frederick 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.SetDirectorySetting

    Frederick Lin shared this idea  · 
  6. 23 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Frederick Lin supported this idea  · 
  7. 208 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    13 comments  ·  Microsoft 365 Groups  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment An error occurred while saving the comment
    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  · 
  8. 1,634 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    42 comments  ·  Microsoft 365 Groups  ·  Flag idea as inappropriate…  ·  Admin →

    We’ve recently shipped the ability to change the SharePoint Site URL associated with a Microsoft 365 Group (formerly Office 365 Group). https://www.microsoft.com/en-us/microsoft-365/roadmap?filters=&searchterms=56205. This can be done via the SharePoint Admin Center. The site URL can be changed on a per-site basis, but currently we don’t have plans to allow admins to change the global default from “/sites” to something different.

    An error occurred while saving the comment
    Frederick 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  · 
  9. 80 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Microsoft 365 Groups  ·  Flag idea as inappropriate…  ·  Admin →
    Frederick Lin supported this idea  · 

Feedback and Knowledge Base