When configuring the connection from SCOM 2012 to Azure Operational Insight, there are some steps that are not that obvious. SCOM will alert you that the connection has issues, but it’s not that clear why. Here are some alerts I noticed when I initially configure Azure Operational Insight:
Description: Advisor is failing to send operational data to service.
A proxy server or your network settings might be misconfigured or there is a temporary network problem. Check the Knowledge Tab for possible resolutions. The context of where the alert appears might indicate whether the problem is due to a proxy server configuration or some other
Alert: Advisor failed to download the latest advisor knowledge management packs
Description: Event Description: Failed to synchronize the latest Management Package information from Advisor Cloud service. Wait for the next cycle to retry
Alert: Advisor connector failed to send analysis data to management server
Connector Framework Alert Write Action Last modified time
Description: One or more data batch was dropped dropped after exceeding retry time.
This indicates that some data was not uploaded to Advisor for some time and was lost ; there should be additional Alerts pointing at the root cause as to why data was failing to be sent in the first place. Typical reasons include but are not limited to problems with DNS name resolution, failed SSL connection, network timeout and proxy settings. Check the Knowledge Tab for possible resolutions.
SatyaVel from Microsoft postet some very use information on how to troubleshoot Azure Operational Insight connection issues here: http://blogs.technet.com/b/momteam/archive/2014/05/29/advisor-error-3000-unable-to-register-to-the-advisor-service-amp-onboarding-troubleshooting-steps.aspx