![]() ![]() In the following diagram, we can see the Autodiscover client will have to pass through many nodes in his journey, before he is able to complete the Autodiscover journey and get to his “final destination” (number 4 in the diagram). The journey is quite long, and we will need to have some patience to be able to accompany the Autodiscover client in the journey.īefore we will get into the details, is important that we will be able to see the “big picture” or the major nodes that will participate in the Autodiscover journey in Office 365 and Exchange Online environment. In the next sections, we will get into the very specific details of every step that include in the Autodiscover process in the Office 365 environment. The Autodiscover long journey in Office 365 and Exchange Online environment The only purpose of the Autodiscover Journey is very simple – to get an Autodiscover response that includes the required configuration setting for a new Outlook mail profile + infrastructure about existing Exchange web services. All the rest of the hosts who involved in the Autodiscover process in an Office 365 environment, serve as a “logical routers” that will lead and redirect the Autodiscover client to his destiny. In reality, only the last node is the “truth Autodiscover Endpoint”. (The default assumption of the Autodiscover client is that each of these “elements” is the required Autodiscover Endpoint (potential Autodiscover Endpoint). Soon, we will see that the Autodiscover client will meet a couple of “elements”. The term “Autodiscover Endpoint”, relates to each of the nodes or the hosts who will be involved in the Autodiscover process. In this scenario, I added my description\explanation although we cannot see “evidence” for this Autodiscover process in the ExRCA report. For example, the process in which the Autodiscover client provides his credentials to the Autodiscover Endpoint doesn’t appear in the ExRCA report. Note: Although the ExRCA a very detailed information, some of the “Autodiscover steps” is not mentioned in the ExRCA results report. We use the excellent ability of the ExRCA, to display a very detailed report that describes in a very clear and precise way the steps that implemented in the Autodiscover process. In this article, the Autodiscover client is the ExRCA (the Microsoft web diagnostic tool). The Autodiscover client could be – mail client such as Outlook, mobile devices (ActiveSync client) and so on. The client is the entity that needs the required information from the Autodiscover Endpoint. In the next sections, will dive under the “Autodiscover hood” and watch every step and process that are involved in an Autodiscover process in Office 365 and Exchange Online environment.īefore we start, let’s define the factors that are involved in the process. What matters is the “final results” meaning – did the Autodiscover client manage to complete the Autodiscover journey successfully or not. Part of the Autodiscover process includes “built-in failures”.There are many “moving parts” and many available paths for the Autodiscover journey.The Autodiscover process is a very “smart” and intelligent mechanism, which manages to survive in a complex and complicated environment.The number of the “parts” depend on many variables but the important observations from the “Autodiscover journey” are: The number “ 20”, is just an arbitrary number because, the “Autodiscover Journey” can be dived even to more parts or fewer parts. I have tried to separate each of these steps and came with a result of 20 different parts. The Autodiscover in Office 365 environment includes many steps. Analyzing the Autodiscover process | Steps described in details. ![]() Using the Microsoft remote connectivity analyzer – the prefix.The Autodiscover long journey in Office 365 and Exchange Online environment.Autodiscover flow in an Office 365 based environment | The article series. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |