O365 connection fails with time out

[#1]

Summary

This article covers why the O365 connection may fail with a time out error

Symptoms

We check the new functionality of FNMS 2016 and we try to connect to our O365 Portal. This process fails with time out error.

016-09-15 14:30:29,143 [ERROR]     System.Management.Automation.CmdletInvocationException: The remote server returned an error: (504) Gateway Timeout. ---> System.Net.WebException: The remote server returned an error: (504) Gateway Timeout.
   at Microsoft.Rtc.Management.Common.AutoDiscoverClient.QueryAutoDiscoverService(String queryUrl)
   at Microsoft.Rtc.Management.Common.AutoDiscoverClient.DiscoverUrl(String autodiscoverEndpoint, String desiredLink, Int32 numOfHops)
   at Microsoft.Rtc.Management.Common.AutoDiscoverClient.DiscoverUrlForDomain(String discoveryServiceUrl, String domainToken, String desiredLink)
   at Microsoft.Rtc.Management.OnlineConnector.GetPowerShellEndpointCmdlet.BeginProcessing()
   at System.Management.Automation.Cmdlet.DoBeginProcessing()
   at System.Management.Automation.CommandProcessorBase.DoBegin()
   --- End of inner exception stack trace ---
   at ManageSoft.Compliance.Importer.Logic.PowerShellDataReader.Read()
   at System.Data.SqlClient.SqlBulkCopy.ReadFromRowSourceAsync(CancellationToken cts)
   at System.Data.SqlClient.SqlBulkCopy.WriteToServerInternalAsync(CancellationToken ctoken)
   at System.Data.SqlClient.SqlBulkCopy.WriteRowSourceToServerAsync(Int32 columnCount, CancellationToken ctoken)
   at System.Data.SqlClient.SqlBulkCopy.WriteToServer(IDataReader reader)
   at ManageSoft.Compliance.Importer.Logic.DatabaseConnection.LoadData(IDataReader p_DataReader, String p_TableName, Int32 p_BatchSize, Boolean p_ExplicitColumns)
   at ManageSoft.Compliance.Importer.Logic.XML.SourceToTarget.ExecuteReader(IExecutionContext context, ISourceConnection sourceConn, IDataReader reader)
   at ManageSoft.Compliance.Importer.Logic.PublicObjectModel.SourceToImportedTableObject.ExecuteReader(IValidatingDataReader reader, SourceToObject STOObject)
   at ManageSoft.Compliance.Importer.Logic.PublicObjectModel.SourceToObjectImplementation.ExecuteImplementationSQL(IExecutionContext context, SourceToObject sourceToObject)
   at ManageSoft.Compliance.Importer.Logic.XML.Reader.Execute(IExecutionContext context)
   at ManageSoft.Compliance.Importer.Logic.ActionExecuter.ReaderExecuter.ExecuteSingleReader(Reader reader, Int32 procedureOrder, Version sourceDatabaseVersion)
   at ManageSoft.Compliance.Importer.Logic.ActionExecuter.ReaderExecuter.Execute()
   at ManageSoft.Compliance.Importer.Logic.ComplianceImporter.ProcessExecution(ComplianceReader p_ComplianceReader, Tenant p_Tenant, IExecutionContext p_Context)

Resolution

Try running the cmdlet again, but instead specify the -OverrideAdminDomain parameter. Use the default domain that was included with your Office 365 subscription; for example, use ExampleCompany.onmicrosoft.com. The PowerShell cmdlet should resemble the following: Import-Module SkypeOnlineConnector $Credential = Get-Credential $Session = New-CSOnlineSession -credential $Credential -OverrideAdminDomain ?ExampleCompany.onmicrosoft.com? This is because it may be related to a known issue, there is more information on this issue found here: http://www.ucblog.co.uk/?p=25