With the new OWA, the “pod” address for the mailbox server no longer appear in the URL. An autodiscover configuration will reveal that accounts now use some sort of [guid]@domain.com for the server. This post will explain how to get the server for your account.
Step 2: Connect to Exchange using Powershell:
$UserCredential = Get-Credential
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell/ -Credential $UserCredential -Authentication Basic -AllowRedirection
Step 3: Query Exchange Online to get the list of GUIDs, optionally output to a file if you have a huge number of users that will not fit into the screen
Get-Recipient | select Alias, ExchangeGuid
Get-Recipient | select Alias, ExchangeGuid > c:\o365.txt
Step 4: Note the guid for the account that you want to manually configure.
Step 5: Start the outlook account settings manual configuration process and use the follow settings:
More Settings > Connection
Connect to Microsoft Exchange using HTTP: Yes (checked)
More Settings > Connection > Exchange Proxy Settings
Proxy Server for Exchange: outlook.office365.com
Only connect to proxy servers that have this principal name in their certificate: msstd:outlook.com
On fast and slow networks...: Yes (checked)
Proxy authentication settings: Basic Authentication
Note that if for any reason you have to resort to a manual configuration like this, chances are some features will not work as per Microsoft’s documentation and the tech support folks in the forums will also be clueless as to how to help you since there are too many possible grounds to cover. It is claimed that features such as User Archive, Out of Office, Calendar etc. may behave erratically or not appear or function at all.