Feedback by UserVoice

Tim

My feedback

  1. 195 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    10 comments  ·  General » Users, Photos, Contacts  ·  Flag idea as inappropriate…  ·  Admin →
    Tim supported this idea  · 
    Tim commented  · 

    especially useful for guest accounts where I want a consultant to have access but not forever as I understand it this may not be considered very critical for AD sync'd users since a sync'd user account once expired will change to disabled and set the block login in AAD upon next sync but with cloud only users I need to have an expiration to block access and require review if still needed after it fails closed. This is a basic an necessary stop gap measure.

  2. 1,796 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    87 comments  ·  Office 365 Admin  ·  Flag idea as inappropriate…  ·  Admin →
    Tim supported this idea  · 
  3. 10,138 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    358 comments  ·  Office 365 Admin  ·  Flag idea as inappropriate…  ·  Admin →
    Tim supported this idea  · 
    Tim commented  · 

    In our case our AAD existed for several years and was used for Azure prior to licensing O365. With Azure the tenant name did not matter much and was not visible for most things. Now we have significant usage of Azure and AAD and as we look to deploy O365 the tenant name is not ideal for branding internally with users or externally while sharing files with SharePoint, OneDrive, Teams etc. Microsoft Azure experts suggest that given the complexities with Azure, AAD, AADC and so forth that their advice would be to avoid a tenant migration but if we want the tenant name changed that is the only way to accomplish it and we should engage a partner.

    Ideally, we would like a vanity URL capability to apply to all of the various places that the tenant name is exposed. We would also like the ability to apply a different vanity URL default per user or group. For example, <CORP-DOMAIN>, <BUSUNIT1-DOMAIN>,<BUSUNIT2-DOMAIN> where individual business units may operate under separate email domains while part of one central CORP IT.

    Tim commented  · 

    <VOTE HERE TOO>
    https://office365.uservoice.com/forums/273493-office-365-admin/suggestions/10285887-make-is-possible-to-change-tenant-name-in-office365

    In our case our AAD existed for several years and was used for Azure prior to licensing O365. With Azure the tenant name did not matter much and was not visible for most things. Now we have significant usage of Azure and AAD and as we look to deploy O365 the tenant name is not ideal for branding internally with users or externally while sharing files with SharePoint, OneDrive, Teams etc. Microsoft Azure experts suggest that given the complexities with Azure, AAD, AADC and so forth that their advice would be to avoid a tenant migration but if we want the tenant name changed that is the only way to accomplish it and we should engage a partner.

    Ideally, we would like a vanity URL capability to apply to all of the various places that the tenant name is exposed. We would also like the ability to apply a different vanity URL default per user or group. For example, <CORP-DOMAIN>, <BUSUNIT1-DOMAIN>,<BUSUNIT2-DOMAIN> where individual business units may operate under separate email domains while part of one central CORP IT.

Feedback and Knowledge Base