Announcement: New SCOM Management Pack for Microsoft 365
Published Jun 04 2021 11:01 AM 46.7K Views
Microsoft

Refer to the latest version at SCOM Microsoft 365 V2.

=============================

Update on Aug13th 2021

We are LIVE with M365 MP!

It has been a couple of months of CTP release, and we have had overwhelming responses (250+ downloads) from M365 MP users which has helped immensely in shaping the GA release. Of course, the work is not over, we are constantly looking to improve the MP experience based on your feedback and we hope to bring more updates to this MP in few months. The latest version of the MP can be downloaded here and it can be upgraded from CTP to GA.

 

Upcoming updates:

  • Improved Alert mechanism from Microsoft 365 Service Communications.
  • Additional Modern Authentication with Certificate.
  • Monitor multiple SKUs with single watcher node.
  • Improved M365 Network Connectivity Monitoring & Dashboards.

As always, feel free to provide your feedback at M365 MP Feedback.

 

We also like to announce the availability of SquaredUp dashboard pack for the new Microsoft M365 management pack. It is a neat set of dashboards for all the key metrics related to M365 workflows on all watcher nodes. To find out more about SquaredUp for SCOM, click here.

The dashboard pack consists of one high-level overview dashboard with the status and key performance indicators. As you drill down into the watcher nodes themselves, there are also a bunch of perspectives pertaining to each M365 service configured. These perspectives display the data scoped specifically to the watcher node you drill into.

 

AakashMSFT_0-1628840485261.png

 

================================

[06/04] The wait is over!

 

Today, we announce the Management Pack for monitoring Microsoft 365 in its CTP (Community Technical Preview) form. This has been a long pending ask amongst SCOM Customers and now, it is available for you to monitor Microsoft 365 workload. Detail of the Management Pack are shared below, and we request you to take a look at the Guide while installing the MP.

 

As early adopters of this Management Pack release, you provide valuable insight into how the platform works at enterprise scale and help us ensure our customers continue to have a wonderful experience with SCOM. Feel free to write to us at M365 MP Feedback with your feedback & suggestions.

 

Here we go

 

For IT organizations, the shift toward Software-as-a-Service can be a daunting move. The perceived lack of control can often hinder this transition, as the IT organization struggles with the role of service broker rather than service provider. As customers make that move to Microsoft 365, a common challenge is the need for service capability monitoring to provide visibility to service health and performance.

Less than 20% of the users open a Service ticket if they encounter any performance issues. If an IT Admin is not aware of any issues, the org is bound to face productivity and financial losses. Microsoft 365 Management Pack for SCOM helps continuously measure M365 user experience from multiple locations using synthetic transactions that user perform and alerts you in case of service degradation. It also provides you with actual Quality of Service delivered to M365 users.

 

Few key features of M365 MP are listed below

  • All in one: Get centralized reports on Microsoft 365 monitoring on SCOM console.
  • Easy to install and setup - Wizard based approach.
  • Analyze sites with low performance and work towards alleviating the blockages, in turn increase ROI on M365 investments.
  • Add Microsoft 365 subscriptions and configure endpoints (watcher nodes) to perform synthetic transactions.
  • All new HTML dashboards with visualization of performance metrics across Exchange, SharePoint, Teams, Licenses and Network.
  • Proactively monitor connection health for the subscriptions and endpoints accessibility.
  • Reflect Microsoft 365 Incidents, Message Center, and Planned Maintenance messages for the subscription to the Operations Manager alerts.

Upcoming updates:

  • Improved Alert mechanism from Microsoft 365 Service Communications.
  • Additional Modern Authentication with Certificate.
  • Support for monitoring GCC High subscriptions.
  • Improved M365 Network Connectivity Monitoring & Dashboards.

 

Refer to below GIFs which will guide you in setting up this MP in a matter of minutes. And again, your feedback & suggestions are invaluable. Reach us at M365 MP Feedback.

 

Easy setup with Wizard

Subscription setup

 

Steps to Add SubscriptionSteps to Add Subscription

 

Watcher Node setup

 

Steps to Add Watcher NodeSteps to Add Watcher Node

 

H5 Dashboards on Web Console

 

M365 Dashboards on Web ConsoleM365 Dashboards on Web Console

51 Comments
Copper Contributor

Has anyone managed to get the Teams Connection Monitor working all I get is 

ERROR: Unable to find Team name 'TeamName' State: Critical. Exception: System.Exception: Team not found.
at Microsoft.SystemCenter.M365.ManagedModules.TeamsPerformance.GetTeamId()

Copper Contributor

Same here Srobyeah , We got the M365 Subsciptions, Service Status and Licenses working. But teams refuses to be found. @AakashMSFT Any tips? (Prerequisites and Test Connection is green!)

TeamsPerformance ERROR: Unable to find Team name 'SCOM_M365_TEST'. State: Critical. Exception: System.Exception: Team not found. at Microsoft.SystemCenter.M365.ManagedModules.TeamsPerformance.GetTeamId().

 

MishaYang_0-1623914855641.png

 

Microsoft

@MishaYang , @Srobyeah - We recognize this issue and may have a fix ready. Please write to us at M365 MP Feedback with the above details and we will share the fix.

Copper Contributor

@AakashMSFT The updated MP build works great for me

Thanks for the help

Copper Contributor

@AakashMSFT Seems to work for Teams Connectivity! Working on Teams Performance and will get back to you! Thank you! :cool:

Copper Contributor

Hi, I would like to use a SCOM Management Server to act as a Watcher node, because at the moment only Management have access the Internet. It is is possible at this stage to do this ?  

 

Thank you !

Joannis

 

Copper Contributor

Hi, is there different network connectivity requirements for the SCOM console/management server to O365 than it is for the watcher nodes ?

I found the requirements for the watcher nodes in the doc, but not for management server.

 

It's needed because I have to ask white listing of o365 URLs in our proxys server and Firewall.

Thank you  

Copper Contributor

Hi, Has anyone gotten the Sharepoint Setup to work? I'm not sure what format it is expecting for the document library and sharepoint site. I've used both formats displayed below the field, and I've kept document library to just "Documents". 

 

This is the error we are seeing - 

< Data > SharePointPerformance ERROR: Unable to find site named 'M365SCOM' on SharePoint site 'domain.sharepoint.com/M365SCOM'. State: Critical. Exception: System.IO.InvalidDataException: 'M365SCOM' not found at Microsoft.SystemCenter.M365.ManagedModules.SharePointPerformance.GetSiteId(String strParentSiteId, String strSiteName) </ Data >

 

M365SCOM is a public group I recently created.

 

I've edited the above error to remove our sharepoint domain name.

Microsoft

@Joannis35 - Not yet - we will look into it post GA.

Microsoft

@Eric Delmotte Its the same requirement, although most of the actions are performed on Watcher node, we still need internet connectivity on MS for authentication and setup.

Microsoft

@hhawthorne This is a current limitation. SharePoint Synth Transactions can be performed only on Root site i.e Documents library on 'domain.sharepoint.com' and not under M365SCOM.

Copper Contributor

Is it possible to monitor all licenses from one watcher or each watcher can monitor just one license?

Copper Contributor

I have the same question as @Fursel 
We have a lot of different licenses in our environment, and would like to know if there is a way to automatically monitor all of them.
If we need to configure 20-30 different watchers to be able to monitor our licenses, this is almost impossible, especially when new licenses are added regularly.

 

Kr,

Frederik

Copper Contributor

Is this free of cosT >

Copper Contributor

Hi @AakashMSFT , when adding a subscription I get the following error: "AppRoleAssignment creation exception". 

Copper Contributor

Hello I am trying to Configure the Watcher node only to do "Mail Flow" so I have a couple of questions:

#1.) Is Prerequisite for Teams network assessment required?

#2.) We didn't install the Teams network assessment, can you help with the following errors:

Log Name: Operations Manager
Source: Health Service Modules
Date: 9/3/2021 9:39:08 AM
Event ID: 950
Task Category: None
Level: Error
Keywords: Classic
User: N/A

Description:
The description for Event ID 950 from source Health Service Modules cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

MailFlowExchangeToM365
ERROR. Message: System.Exception: Unable to acquire authorization token. Possible connectivity issue.
Exception: An error occurred while sending the request. ---> System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: The remote name could not be resolved: 'login.microsoftonline.com'
at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult, TransportContext& context)
at System.Net.Http.HttpClientHandler.GetRequestStreamCallback(IAsyncResult ar)
--- End of inner exception stack trace ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Identity.Client.Platforms.net45.Http.DnsSensitiveClientHandler.<SendAsync>d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Identity.Client.Http.HttpManager.<ExecuteAsync>d__10.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Identity.Client.Http.HttpManager.<ExecuteWithRetryAsync>d__8.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Identity.Client.Http.HttpManager.<SendPostAsync>d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Identity.Client.Http.HttpManager.<SendPostAsync>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Identity.Client.OAuth2.OAuth2Client.<ExecuteRequestAsync>d__11`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Identity.Client.OAuth2.OAuth2Client.<GetTokenAsync>d__10.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Identity.Client.OAuth2.TokenClient.<SendHttpAndClearTelemetryAsync>d__8.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Identity.Client.OAuth2.TokenClient.<SendTokenRequestAsync>d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Identity.Client.Internal.Requests.RequestBase.<SendTokenRequestAsync>d__20.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Identity.Client.Internal.Requests.ClientCredentialRequest.<FetchNewAccessTokenAsync>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Identity.Client.Internal.Requests.ClientCredentialRequest.<ExecuteAsync>d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Identity.Client.Internal.Requests.RequestBase.<RunAsync>d__13.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Identity.Client.ApiConfig.Executors.ConfidentialClientExecutor.<ExecuteAsync>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.SystemCenter.M365.ManagedModules.Helpers.RestManagedModule`1.InitializeRest()
--- End of inner exception stack trace ---
at Microsoft.SystemCenter.M365.ManagedModules.Helpers.RestManagedModule`1.InitializeRest()
at Microsoft.SystemCenter.M365.ManagedModules.MailFlowExchangeToM365.DoWork(Dictionary`2 dictionary)

the message resource is present but the message is not found in the string/message table

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Health Service Modules" />
<EventID Qualifiers="0">950</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2021-09-03T13:39:08.099784500Z" />
<EventRecordID>643955</EventRecordID>
<Channel>Operations Manager</Channel>
<Computer>removed</Computer>
<Security />
</System>
<EventData>
<Data>MailFlowExchangeToM365
ERROR. Message: System.Exception: Unable to acquire authorization token. Possible connectivity issue.
Exception: An error occurred while sending the request. ---&gt; System.Net.Http.HttpRequestException: An error occurred while sending the request. ---&gt; System.Net.WebException: The remote name could not be resolved: 'login.microsoftonline.com'
at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult, TransportContext&amp; context)
at System.Net.Http.HttpClientHandler.GetRequestStreamCallback(IAsyncResult ar)
--- End of inner exception stack trace ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Identity.Client.Platforms.net45.Http.DnsSensitiveClientHandler.&lt;SendAsync&gt;d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Identity.Client.Http.HttpManager.&lt;ExecuteAsync&gt;d__10.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Identity.Client.Http.HttpManager.&lt;ExecuteWithRetryAsync&gt;d__8.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Identity.Client.Http.HttpManager.&lt;SendPostAsync&gt;d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Identity.Client.Http.HttpManager.&lt;SendPostAsync&gt;d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Identity.Client.OAuth2.OAuth2Client.&lt;ExecuteRequestAsync&gt;d__11`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Identity.Client.OAuth2.OAuth2Client.&lt;GetTokenAsync&gt;d__10.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Identity.Client.OAuth2.TokenClient.&lt;SendHttpAndClearTelemetryAsync&gt;d__8.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Identity.Client.OAuth2.TokenClient.&lt;SendTokenRequestAsync&gt;d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Identity.Client.Internal.Requests.RequestBase.&lt;SendTokenRequestAsync&gt;d__20.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Identity.Client.Internal.Requests.ClientCredentialRequest.&lt;FetchNewAccessTokenAsync&gt;d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Identity.Client.Internal.Requests.ClientCredentialRequest.&lt;ExecuteAsync&gt;d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Identity.Client.Internal.Requests.RequestBase.&lt;RunAsync&gt;d__13.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Identity.Client.ApiConfig.Executors.ConfidentialClientExecutor.&lt;ExecuteAsync&gt;d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.SystemCenter.M365.ManagedModules.Helpers.RestManagedModule`1.InitializeRest()
--- End of inner exception stack trace ---
at Microsoft.SystemCenter.M365.ManagedModules.Helpers.RestManagedModule`1.InitializeRest()
at Microsoft.SystemCenter.M365.ManagedModules.MailFlowExchangeToM365.DoWork(Dictionary`2 dictionary)</Data>
</EventData>
</Event>

Copper Contributor

Does anyone have an idea on how to get a Historical report for Office 365? I need to have a month-on-month report of my Office 365 tenant ready for the management.

Copper Contributor

Hi @AakashMSFT, any chance to have Teams synthetic transactions for Inbound/Outbound calling like it used to be with Skype for Business on-premise? I know you have a SIP Tester tool but would love to see something for SCOM in the future, so we can for example monitor Direct Routing via SCOM.

Microsoft

@Fursel @FrederikLacroix - We are looking to provide this enhancement in the upcoming update.

@ramki40 - Yes - it is free of cost and supported by Microsoft.

@alexpowell @DannK - Please share details on your suggestions/issues at m365mp@microsoft.com.

 

Copper Contributor

Thank you Aakash. I will send a suggestion. Fingers crossed Microsoft will add this in the future.

Copper Contributor

Great job ! Is it possible to install it on SCOM 2012 R2 version (with 2012 Windows Server) ?

Copper Contributor

Is it possible to add to the Sharepoint test the deletion of files used for the test after script execution?

Copper Contributor

Is it possible to move "M365 Connection State Monitor" to watcher node instead test directly from management server?

Copper Contributor

@AakashMSFT Aakash, For the watcher nodes - A bit of confusion for M365 send and receive accounts.  What are the license requirements for these accounts?  Are the same accounts are used for Sharepoint, Teams, and Network monitoring?   Thanks for your help.

Copper Contributor

Hi!

 

I stuck at install watcher node. Network ports and reqs opened to internet and ms services.

On the mp server i see

Running verify prerequisites task on agent 'srv1'...
Task canceled because it ran too long.

 

On srv1 in event log i dont see any error, and:

VerifyPrerequisites : Script finished. Returning: 'Prerequisite=PowerShell Version 5:AlreadyInstalled;

Prerequisite=.Net Version 4.7.2 or greater:AlreadyInstalled;

'.

 

Seems script or agent havent read response from srv1, but runas accounts have admin right =)

 

What i doing wrong ?)

Copper Contributor

Hi. i am using a previous version of Office 365 Management Pack (I believe version 7.2.0.0) . I understand that the Graph API is going to be decomm'd by end of year by Microsoft.

 

if this is the case, does this mean the previous version of O365 MP will stop working? And that I will need to upgrade to this latest M365 MP if I would like to continue to monitor "Microsoft 365 Incidents" and "Message Center"?

Copper Contributor

Hello there,

I am trying to install the prerequisites for the watcher server and I am receiving the following error :

 

Running verify prerequisites task on agent 'ServerName'...

The user "UserID"  does not have sufficient permission to perform the operation. The "UserID" has admin rights on SCOM and on the agent .

 

Any ideas?

 

Thanks

 

Copper Contributor

Hi
After installing the 365MP, I get the following error message when I click the "Create" button and enter ID and password.
The specified ID has the privileges of a global administrator.
The same symptoms occur in SCOM2022Preview.
What should I check?

Try Again.
Azure Application creation exception

Microsoft

@Keishi_Horiuchi There has been few changes on the AAD APIs and it is breaking "Add Subscription" feature. We will be fixing this issue in upcoming release. Please manually create subscription until then.

Copper Contributor

@AakashMSFT
Thank you for your comment.
The setup is complete thanks to the detailed documentation attached.
Completed with scom2019 and scom2022preview.

 

Copper Contributor

Hi. 
Cant add Watcher note 

Recive this error 

The synthetic transaction did not run successfully. Error message:

System.Net.WebException: The remote server returned an error: (403) Forbidden.
at System.Net.HttpWebRequest.GetResponse()

Items to check:
• Are the endpoints above correct?
• It can take some time to get the credentials distributed to the agent, so you may want to wait a minute and try the test again.
• Check the Operations Manager event log on the agent for details.
• Refer to the Troubleshooting appendixes in the User Guide.
• Ensure that the firewall on the agent allows connection to Microsoft 365 (see the Network, Firewalls & Proxy section in the User Guide).
• Ensure that a proxy is established, if required (see the Configure proxy connection section in the User Guide).


Azure signin log for Service preciple reports 

Status

Success

/Kristoffer 
Copper Contributor

@AakashMSFT we managed to setup the teams monitoring. However the teams network performance are not showing up in SCOM. upon investigating we found the watcher node is unable to contact the relay IP. Due to security reasons, we are unable to open the port for IP addresses but we can communicate the urls from the browser. 

 

My question, is there a way network assessment tool could use the url instead of a relay IP?

 

Thanks,

Copper Contributor

On 1/3 just after 9am PST it seems something change causing the M365 Connection State Monitor to trigger.  The updated CTP version of the MP is also affected.

 

 

Copper Contributor

Anybody else have this issue with the Events written by this MP?  Both my production and pre-production watcher have this issue.  Seem to be for all the new Event IDs not just 961

 

The description for Event ID ( 961 ) in Source ( Health Service Modules ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event:

Copper Contributor

@StephenMorrison we have also had alerts for the M365 Connection State Monitor recently, but they started around 01st December and not resolving.

 

We also get the same Event ID behaviour you mentioned, for Events 970/965 - TeamsNetworkAssessment, 910 - PortalLogin, 931 - LicenseCount, 920 - ConsumedUnits, 966 - TeamsPerformance, 940 - LicenseVerification

 

We haven't enabled SharePoint or Exchange yet, but no doubt they will do this too.  Sounds like the Management Pack needs to be updated to register these Events properly.

 

A very convoluted Management Pack I feel - especially to get watchers working properly, as we have hit and miss test results which leaves you second guessing...

Copper Contributor

We also have the Teams Performance Monitor monitor intermittently alerting on each watcher, about 2-3 times a day :(

Copper Contributor

@Steve_Cahill , We created overrides for many of the tests to have to include multiple failures to stop this.  Our tests would fail to complete randomly causing alerts.  This might be improved with the next version. They are moving away from the Skype assessment tool to a teams assessment tool.  Hopefully that will be more reliable. 

Copper Contributor

Maybe the top of this article should include that the MP has been updated twice since Aug!  A new release came out in Dec, then another 6 days ago:
https://www.microsoft.com/en-us/download/details.aspx?id=103379 

Copper Contributor

@StephenMorrison - the connection fix is included in the new MP documentation.  Mine is now connecting - after updating my subscription to use the new Graph URL and following the API permissions config under section Upgrading from Microsoft 365 MP Version 10.1.100.0

Copper Contributor

Hi guys,

 

I have followed the word doc to this MP, and everything during setup checks out fine, but no data presents in Console, H5 (Web OPS) or our SquaredUp?

I'm i doing anything wrong?

Copper Contributor

@Rasmus_Nor how long have you waited for data?  My dashboards took a long time to populate.  

Copper Contributor

@StephenMorrison , i have been waiting for 5 days now.

Copper Contributor

@Rasmus_Nor perhaps you are using the old version of the MP? Our data started populating within about 5-10 mins.  There is a newer version here, which has the newer graph url: https://www.microsoft.com/en-us/download/details.aspx?id=103379

Copper Contributor

@Steve_Cahill 

It is the new version of MP i have installed.

From our SCOM (2019 with latest CU) after downloading and trying to install the MP you are linking to:

//
A management pack contained in Microsoft 365 bundle (version 10.1.270.0) has already been imported. To remove this bundle from the import list, right-click the bundle and click Remove.

\\

We are running the newest MP and SCOM version.

Copper Contributor

@Rasmus_Nor I assume that you have set up the connection AND one or more watchers (all via the Administration node)?  When you do this is tests them too.

 

If you haven’t set up any watchers and have only set up the subscription connection itself, no other data is visible in the console views (from memory) because all of the Rules relating to subscription alerts and incidents are disabled by default.

 

Other than that, I would be checking Application Event Log events on the Management Server to see how it is behaving.

Copper Contributor

@Steve_Cahill - Thats korrect - i have set the M365 connection up on 3 MS tenants (not at once) to two Watsher servers.
Thoes times it offeret to test pre-reqs along the way i tested, and everything was fine.

I our SquaredUp th Sub and Watchers say everything is fine but no info shows in SquaredUp, SCOM Console and Web/HTML5:

Rasmus_Nor_0-1648211317431.png

 

Der is not any entrys in Eventlog on all the servers.

Copper Contributor

Yeay! :)
I´ve got it working!
The agent on the Worker server was not updated to latest agent version.
Thanks for the help, guys.

Copper Contributor

@Rasmus_Nor , interesting.  Recently I had all my M365 workloads stop running on my watcher. The agent was running and showed healthy.  All my performance dashboards stopped showing new data points and no m365 events where being written.  I restarted the MMA and it started to function again.  I wonder if the upgrade of the agent fixed it or the restart of the service.  

Copper Contributor

Anybody else getting this type of failure?  We haven't adjusted the polling cycle of anything.  Not sure why we are getting throttled.

 

M365 Mailbox Count M365 Monitor: Failure, Description: This monitor is unable to determine the number of mailboxes that exist under M365 and/or the associated organization's location. Unable to determine Microsoft 365 mailbox count. Reason: ERROR - Unable to get mailbox report data. State: Critical. Exception: System.Net.WebException: The remote server returned an error: (429) ServiceThrottleThresholdExceeded. at System.Net.HttpWebRequest.GetResponse() at Microsoft.SystemCenter.M365.ManagedModules.Helpers.SimpleRestClient.MakeCallWithResponseInternal(String url, Dictionary`2 headers, String postData, String httpVerb, String contentType) at Microsoft.SystemCenter.M365.ManagedModules.Helpers.SimpleRestClient.MakeCallWithResponse(String url, Dictionary`2 headers, String postData, String httpVerb, String contentType) at Microsoft.SystemCenter.M365.ManagedModules.Helpers.RestManagedModule`1.InvokeRestMethod(String uri, String verb, String strPostData, String contentType, Dictionary`2 customHeaders) at Microsoft.SystemCenter.M365.ManagedModules.MailboxCountM365.GetMailboxReport().

Copper Contributor

@StephenMorrison , i´m sure that in my case it was a matter of upgrading the agent.
Last week i´ve had the whole Watcher server restartet and still no data.

Co-Authors
Version history
Last update:
‎Jan 23 2023 11:35 PM
Updated by: