Programming Tutorials

Is autodiscover CNAME a must in Office 365

By: Ashley in Office365 Tutorials on 2012-06-12  

The Autodiscover service makes it easier to configure Outlook 2007 or Outlook 2010 and some mobile phones. You can't use the Autodiscover service with earlier versions of Outlook, including Outlook 2003. In earlier versions of Microsoft Exchange (Exchange 2003 SP2 or earlier) and Outlook (Outlook 2003 or earlier), you had to configure all user profiles manually to access Exchange. Extra work was required to manage these profiles if changes occurred to the messaging environment. Otherwise, the Outlook clients would stop functioning correctly.

The Autodiscover service uses a user's e-mail address and password to automatically configure a user's profile. Using the e-mail address, the Autodiscover service provides the following information to the client:

· The user's display name

· Separate connection settings for internal and external connectivity

· The location of the user's Mailbox server

· The URLs for various Outlook features that govern functionality such as free/busy information, Unified Messaging, and the offline address book

· Outlook Anywhere server settings

When a user's Exchange information is changed, Outlook automatically reconfigures the user's profile using the Autodiscover service. For example, if a user's mailbox is moved or the client can't connect to the user's mailbox or to available Exchange features, Outlook will contact the Autodiscover service and automatically update the user's profile to include the information that's required to connect to the mailbox and Exchange features.

More details at http://technet.microsoft.com/en-us/library/bb124251.aspx

Therefore, you are advised to add the autodiscover CNAME for your domains.

If not added, you will have to manually configure the outlook profile






Add Comment

* Required information
1000

Comments

No comments yet. Be the first!

Most Viewed Articles (in Office365 )

Copy Power Automate Flows from one environment to another

Moving changes from a development environment (sandbox) to a production environment in Dynamics 365

Migration from on-premise exchange 2003 to Office 365

Email limits and message limitations in Office 365

Comparison: SharePoint Online Plan 1 vs SharePoint Online Plan 2

ADFS and ADFS Proxy in Windows Server 2012

Configure IIS as SMTP relay server for Office 365

On-premise Exchange and Lync Online integration

Microsoft Flow to sync data from SharePoint list update/delete records to Dataverse Table

xxxx cannot be loaded because the execution of scripts is disabled on this system. Please see "get-help about_signing" for more details.

Making your Alias email as 'Send As' in Office 365

Steps to create Microsoft Flow to sync data from SharePoint list to Dataverse Table

365 office login (office 365 login)

Create Word, Excel, PowerPoint using Office Web Apps in Office 365

Change Dirsync synchronization frequency

Latest Articles (in Office365)

Copy Power Automate Flows from one environment to another

Moving changes from a development environment (sandbox) to a production environment in Dynamics 365

Microsoft Flow to sync data from SharePoint list update/delete records to Dataverse Table

Steps to create Microsoft Flow to sync data from SharePoint list to Dataverse Table

ADFS and ADFS Proxy in Windows Server 2012

365 office login (office 365 login)

Configure SSO for a domain with ADFS - Convert a domain to a federated domain in Office 365

What is Office 365 Small Business Premium?

What is Ofice 365 Home Premium

What is Office 365 Midsize Business Plan?

Migration from on-premise exchange 2003 to Office 365

Create Word, Excel, PowerPoint using Office Web Apps in Office 365

On-premise Exchange and Lync Online integration

Email limits and message limitations in Office 365

Migrating SharePoint WSS2.0 site to SharePoint Online and Backup the SharePoint Online