Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Powershell session limit on 365 templates?

Hi all,

We have recently started using SAM to monitor our 365 tenant (both Exchange and Teams).

I got things setup and am currently using 'login.microsoft.com' as our external node and have assigned our chosen templates to that node. Once configured, monitoring has been extremely hit and miss - SAM will rarely provide metrics and statuses for more than 3 of my chosen templates at any one time and only then with sporadic connection problems. Worst case it does nothing and all templates show as 'Unknown'.

From the limited amount of info online, I can see there is a 3 session limit on powershell connections for any one account and the errors I get from the each template support this. Whilst I understand why there is a limit, it's extremely frustrating. Can someone tell me, does this mean I can't monitor more than 3 templates at once? Aside from contacting Microsoft to increase the limit, is there another way round this in Orion?

I have logged this as a ticket with Solarwinds support, but 6 days later i've heard nothing so am assuming its not something they want to deal with or have no solution for.

If anyone can offer any help or advice, it would be greatly appreciated as this problem means that we will have no idea what 1000 users are doing on Exchange Online or Teams (without having to pull stats manually from the relevant admin portals).

Thanks in advance.

Simon

PS Apologies if this has been asked before - kind of up against it on timescales to get this deployed ASAFP!

Find more posts tagged with

Accepted answers

All comments

christopher.t.jones123

@-SGregory- this is a rather frustrating limit because even if you do contact Microsoft, increasing that limit is not a permanent change that they will make (at least according to what they've told me in the past). The best course of action I can advise is to use API polling to pull the statistics from Microsoft Graph which doesn't experience the same connection limit as connecting via PowerShell. If you review the OOB API templates and some of the OOB Microsoft 365 Templates that utilize Microsoft Graph you could actually get around some of the API polling limitations by recreating those calls into API calls from a powershell component. Good news is most of the statistics you'd be interested in are available via Microsoft Graph.