Download link: 
➡ Click here: Office 365 connexion
A quick test is to run an Office 365 cmdlet—for example, Get-MsolUser —and see the results. All we had to do was reconnect it, and disconnect the new router. The problems went away..
Hi LarryG, thanks for replying. Initially some of the large mailboxes 5GB plus where finding it really slow and Outlook was timing out in the same way and users where losing their messages when on idle. Setting office 365 connexion AD FS requires the use of a third party SSL certificate. Also do you have more than 1 DNS server in your organisation. Last November, we announced the limited preview of Office 365 Connectors, a brand new experience that delivers relevant interactive content and updates from popular apps and services to Office 365 Jesus. With each plan, you can install the 2016 versions of Word, Excel, PowerPoint, Outlook, and OneNote Access, and Publisher are also included only for PC users. If your EOP subscription is Exchange Enterprise CAL with Services includes data loss prevention DLP and reporting using web servicesthe difference instructions in this topic will work for you.
Why download the Office 365 offline installer? While there is nothing wrong with the web installer, if you often re-install Office, you might prefer to have an offline installer of Office 365 to avoid signing-in to your Office account and downloading huge Office installation files each time you want to install Office on your PC.
Office 365 Exchange Online Mailbox Connection Reports - It's likely that your computer has a newer version installed for example, 4 or 4.
This is a typical highly available setup into Office 365. Ideally this server will be installed as virtual servers on multiple Hyper-V hosts. Think about redundancy, not only in the virtual servers, but in the Hyper-V servers as well. Install one AD FS and one AD FS Proxy on one Hyper-V host and the other AD FS and AD FS Proxy on another Hyper-V host. This prevents loss of service from a hardware failure. Keep in mind that once you are using Single Sign-on with Office 365, you rely on your local Active Directory for authentication. Both video and printed steps have provided to ease your implementation of AD FS and SSO. If you need to add the UPN suffix, please follow these instructions, Example Internal Domain Name — contoso. I generally make an OU for all the Office 365 Services; then create more OUs within that one for all the user accounts, services accounts, groups, servers and computers. This will allow us to filter on user accounts and groups when we enable Directory Synchronization with Office 365. The less number of objects that you sync with Office 365 is better. Keep it clean and neat. This will prevent mistakes and keep you head ache free. Setting up AD FS requires the use of a third party SSL certificate. In a production situation, I would recommend that a single name SSL certificate. Wildcard and multi-name certificates will work, but I like to keep things simple and use a standard SSL certificate in a production situation. Make sure that the common name matches what you plan to call the AD FS server farm. Microsoft best practices recommends that you use the host name, STS secure token service. In the example below, I have used the value sts. Keep in mind that before you can successfully use single sign-on with Office 365, you will need to setup and configure Directory Synchronization. After Directory Synchronization is setup, you will have to license the synchronized user in Office 365. This will provision the services for the user. If they want to access Office 365 from outside the internal network, the AD FS Proxy server needs to be setup and configured.