Feedback by UserVoice

Dwight Holman

My feedback

  1. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  2. 2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Dwight Holman supported this idea  · 
    Dwight Holman shared this idea  · 
  3. 41 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)

    While it is likely that Office 365 will need to leave TLS 1.0 enabled broadly for the near future, we are rolling out TLS 1.2 by default which will allow us to publish updated guidance for Exchange on-premises. Please stay tuned to EHLO blog for further updates — several configuration changes will be necessary to ensure everything works smoothly.

    Dwight Holman supported this idea  · 
    An error occurred while saving the comment
    Dwight Holman commented  · 

    This is a concern for us also. We're considering migration to O365 and it would be great if we could enforce TLS1.2 or better for all applications/clients from the beginning.

  4. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Office 365 Admin » Exchange Admin  ·  Flag idea as inappropriate…  ·  Admin →
    Dwight Holman supported this idea  · 
    Dwight Holman shared this idea  · 
  5. 35 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  General » Users, Photos, Contacts  ·  Flag idea as inappropriate…  ·  Admin →
    Dwight Holman supported this idea  · 
  6. 4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Office 365 Admin » Exchange Admin  ·  Flag idea as inappropriate…  ·  Admin →
    Dwight Holman supported this idea  · 
  7. 41 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Dwight Holman supported this idea  · 
    An error occurred while saving the comment
    Dwight Holman commented  · 

    During evaluation of O365 we encountered difficulty with this also. Our current email system has a shared contacts list that is accessible for web mail users and to desktop clients (via CardDAV), and we expected something equivalent to be available in O365.

    A call to the Office 365 support team confirmed that this really isn't a feature. They actually recommend duplicating contacts to each staff member's personal contact folders?!

    On that basis I am surprised this suggestion doesn't have more votes. What are all the other O365 users doing to effectively share and maintain supplier and customer contacts inside their organisations?

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

    We have put shared contacts in a Public Folder because that seems to be the only way to share contacts that is accessible on both OWA and Outlook Desktop clients.

    Yes I know you can put shared contacts in the GAL, but we want to store details (phone numbers, company name, job title, physical address, etc) than are not supported in the GAL.

    Dwight Holman shared this idea  · 

Feedback and Knowledge Base