SCOM dashboards and business service maps
SCOM dashboards turn the alerts, health states and performance data in System Center Operations Manager into views each team can read: business service maps for management, server and alert views for operations. We connect SCOM read-only, add Azure, Microsoft 365 and ServiceNow, and share the result without giving everyone a console.
Business services
- Services watched
- 24
- Healthy
- 22
- Degraded
- 2
- Order processing, customer portal
- Critical
- 0
Order processing, dependency path
- Web front end Healthy
- Order API Healthy
- Message queue Healthy
- SQL02 cluster Slow disks, 48 ms
- Storage array Healthy
SCOM groups by health
| Group | Objects | Open alerts | Status |
|---|---|---|---|
| Web servers | 12 | 0 | Healthy |
| SQL servers | 8 | 3 | Warning |
| Domain controllers | 6 | 0 | Healthy |
| Exchange servers | 5 | 0 | Healthy |
Example data, for illustration only
Why now
Why rebuild your SCOM dashboards now?
SCOM remains the monitoring engine of many Windows estates. The dashboards on top of it are often older than the servers they watch.
-
A dashboard tool that no longer moves
If the tool behind your service maps is no longer developed, every SCOM, SQL Server or Windows Server upgrade raises the same question: will the maps still work afterwards?
-
Consoles built for operators
The Operations console and the web console are built for operators who know SCOM's classes and objects. Managers want to know whether payroll or the customer portal works, in a view they can open without training.
-
Data spread across tools
Servers sit in SCOM, cloud resources in Azure, incidents in ServiceNow. Answering "is the service up?" means opening three tools and comparing what each one says.
-
SCOM Managed Instance has gone
Microsoft retired Azure Monitor SCOM Managed Instance at the end of September 2026 and points customers to Operations Manager or Azure Monitor. Whichever you choose, the dashboards need a new home.
-
SCOM 2022 mainstream support ends
Operations Manager 2022 leaves mainstream support in April 2027. A move to Operations Manager 2025, with mainstream support until January 2030, is a good time to decide where your dashboards live.
What it covers
What should a SCOM dashboard show?
Six areas, from the business service down to the server. Each is delivered with a dashboard tool that we select, license, implement and support with your team.
Business service maps
Management sees whether each service works, not which server is red.
A slow disk on one SQL Server cluster can hold up order processing, and the SCOM alert names the disk, not the service. We rebuild each business service from the SCOM groups and objects behind it, so health rolls up from the server to the service, to the team's workspace and to a home view of the whole organisation. A map shows how objects depend on each other, and a problem colours every node above it.
What it covers
- Services built from SCOM groups and objects
- Health rolled up from object to service
- A home view of every service
- A dependency map for each object
- Critical services tagged and filtered
How we deliver it
- We list your existing service maps and views with you.
- Each service is rebuilt from the SCOM groups behind it.
- Service owners check the result before it replaces the old view.
- Groups stay the source, so new servers appear on their own.
Order processing, dependency path
- Web front end Healthy
- Order API Healthy
- Message queue Healthy
- SQL02 cluster Slow disks, 48 ms
- Storage array Healthy
Alerts, health and performance
Operators find the alert, the server and its history in one place.
A red icon is not enough: operators need to know when the alert started, which group the server belongs to and how it performed last month. Dashboards read SCOM alerts, health, monitor states and performance history from the data warehouse, which keeps hourly and daily performance data for 400 days by default. Tiles follow SCOM groups, so a server added to a group appears without editing the dashboard.
What it covers
- Alerts by severity and resolution state
- Health, including maintenance mode
- Monitor states
- Performance history from the data warehouse
- Views scoped by SCOM group or class
How we deliver it
- We start from ready-made SCOM views, then adapt them.
- Colours follow SCOM health states; tile thresholds are agreed with your team.
- Each operations team gets its own workspace.
- Your admins learn to build and change tiles.
SCOM groups by health
| Group | Objects | Open alerts | Status |
|---|---|---|---|
| Web servers | 12 | 0 | Healthy |
| SQL servers | 8 | 3 | Warning |
| Domain controllers | 6 | 0 | Healthy |
| Exchange servers | 5 | 0 | Healthy |
Azure, Microsoft 365 and ServiceNow
On-premises servers and cloud services in the same view.
Most services now run partly on-premises and partly in Azure, and their incidents live in ServiceNow. The same dashboards show SCOM next to Azure metrics, alerts and Service Health, Log Analytics queries, Microsoft 365 usage, ServiceNow incidents and changes, and any web API that returns JSON. The service keeps an index of objects and their relationships, not a copy of your monitoring data.
What it covers
- Azure metrics, alerts and Service Health
- Log Analytics and Resource Graph queries
- Microsoft 365 usage and licences
- ServiceNow incidents and changes
- Web APIs, plus PowerShell and SQL through an on-premises relay
How we deliver it
- We agree with you which sources each service needs.
- Each source is connected with the permissions your security team approves.
- Cloud and on-premises parts of a service share one health.
- Every connection is documented for your team.
Customer portal
- Web servers (SCOM) Healthy
- Azure App Service Healthy
- Azure SQL Database Healthy
- ServiceNow incidents 1 open
Alerts and tickets
The team that owns the service hears about it, with a ticket already open.
A SCOM alert that lands in a shared mailbox is easy to miss. Any tile can carry a monitor, based on its state or on a threshold you set. When it turns red, a message goes to a Teams channel or an email address, or an incident opens in ServiceNow and is updated as the state changes; your engineers close it once the fix is confirmed. Notifications can pause during planned maintenance.
What it covers
- Monitors on any tile
- Thresholds you set
- Teams and email notifications
- ServiceNow incidents opened and updated
- Pauses for planned maintenance
How we deliver it
- We agree alert rules with each team.
- Notifications go to the team that owns the service.
- ServiceNow assignment is mapped with your ITSM team.
- Rules are tuned with you once real alerts come in.
Notifications sent
- Order processing Teams, database team
- Customer portal ServiceNow incident
- Payroll No alert
- Domain controllers No alert
Security and hosting
SCOM stays read-only, and no inbound port is opened.
Security teams ask two questions first: what can the tool change, and how does it reach our network? The connection to SCOM uses a Read-Only Operator account, plus read access to the data warehouse, and the scope of that role decides which objects the tool sees. A relay agent on a Windows server makes outbound HTTPS connections only. The service is ISO 27001:2022 certified, and you choose hosting in the EU (Ireland) or in the US.
What it covers
- SCOM Read-Only Operator role
- Scope set by your SCOM user roles
- Outbound HTTPS from a relay on Windows
- ISO 27001:2022 certified service
- Hosting in the EU or the US
How we deliver it
- We review the set-up with your security team before we connect.
- Service accounts and scopes are documented.
- The relay can run on two servers for redundancy.
- Workspace access is given to groups rather than individuals.
Security review
- Read-only SCOM account
- Outbound HTTPS only
- Hosting region: EU
- Sharing limited to your domains
Moving over
How do your current SCOM dashboards carry over?
Most of what you use today has an equivalent. We list what you have, then rebuild it piece by piece.
| What you use today | How we rebuild it |
|---|---|
| Business service maps built on SCOM objects | Services rebuilt from SCOM groups, with health rolled up to a home view of the organisation. |
| Service diagrams drawn by hand | Your Visio or diagrams.net drawings become live diagrams, coloured by the health of each service. |
| Availability against SLA | Availability against the service level objectives defined on your SCOM monitors. |
| Read-only dashboards for management | Read-only links that use no licence, limited to your email domains, and scheduled PDFs. |
| Links to ServiceNow | ServiceNow incidents opened when a monitored service turns red, and updated as it changes. |
| SCOM data only | SCOM next to Azure, Microsoft 365, ServiceNow and any web API that returns JSON. |
We review what each existing view does before we commit to its equivalent.
How it works
How does a move to new SCOM dashboards work?
Your current dashboards keep running until the new ones have been checked.
- Step 1
Inventory
We list your service maps, dashboards and SLA views, who uses each one, and decide with you what to keep.
- Step 2
Connect
We install a relay agent on one of your Windows servers and connect it to SCOM with a read-only account, then to your other sources.
- Step 3
Rebuild
Services, maps and dashboards are rebuilt from your SCOM groups, and their owners check them against the old views.
- Step 4
Share
Workspaces, sharing rules and scheduled reports are set up for each audience.
- Step 5
Hand over
Your admins learn to change dashboards themselves. After the project, a customer success manager follows up with you.
Deployment
Cloud service or on your own servers?
The cloud service is the default. For teams that keep everything inside their network, there is an on-premises edition.
-
Cloud service
Hosted in the EU (Ireland) or in the US. Monitoring data stays in SCOM and your other tools; the service keeps no copy of it.
-
On your own servers
An on-premises edition runs on Windows Server inside your network, works with SCOM 2016 to 2025 and reads your existing distributed applications.
-
What stays the same
SCOM keeps monitoring, alerting and running its management packs. The dashboards read from it with a read-only account and change nothing in its configuration.
What Neptune delivers
One partner from the inventory to daily use
You deal with one team for the tool, the set-up and the follow-up.
-
Your maps and views, rebuilt
We rebuild the service maps and dashboards your teams rely on, and check them with the people who use them.
-
Licences
We supply the licences for the dashboard tool and keep them in line with your use.
-
Installation and connection
Relay, service accounts, SCOM and your other sources, set up with your infrastructure and security teams.
-
Follow-up
Our consultants stay with you during the project, then a customer success manager follows up.
FAQ
SCOM dashboard questions, answered.
What is a SCOM dashboard?
A view built on the data System Center Operations Manager (SCOM) already collects: alerts, health states, monitor states and performance. SCOM has its own dashboards in the Operations console and the web console. A dedicated dashboard tool adds business service maps that span SCOM and your other tools and read-only sharing with people who have no SCOM access.
Performance trends come from the SCOM data warehouse, which keeps hourly and daily performance data for 400 days by default.
Does it replace SCOM?
No. SCOM keeps monitoring your servers and applications with its management packs. The dashboard tool reads its alerts, health and performance data with a read-only account and shows them next to your other sources.
Which SCOM versions do you work with?
The cloud service connects to the SCOM management groups you run on your own servers, and we check your version and set-up during the first review. The on-premises edition of the tool supports Operations Manager 2016, 2019, 2022 and 2025.
Operations Manager 2022 leaves mainstream support in April 2027; Operations Manager 2025 has mainstream support until January 2030. If an upgrade is planned, we plan the dashboards with it.
Can you rebuild our existing service maps?
Yes. We start from an inventory of your current maps, dashboards and SLA views, then rebuild each service from the SCOM groups and objects behind it. Drawings you keep in Visio or diagrams.net can become live diagrams coloured by health. Each rebuilt view is checked with its owner before the old one is switched off.
Do we need to open a firewall port?
No inbound port. A relay agent on a Windows server inside your network makes outbound HTTPS connections only, and connects to SCOM with a Read-Only Operator account.
Where is the data hosted?
You choose the EU (Ireland) or the US. Monitoring data is queried at the source when a dashboard loads; the service stores an index of objects and their relationships, your dashboard settings and monitor states. It is ISO 27001:2022 certified. If everything must stay on your own servers, the on-premises edition does that.
Can managers see dashboards without a licence?
Yes. Dashboards can be shared as read-only links that use no licence, limited to your own email domains, or sent on a schedule to a mailbox, with a PDF, or to a Teams channel.
Azure Monitor SCOM Managed Instance has been retired: what now?
Microsoft retired Azure Monitor SCOM Managed Instance at the end of September 2026 and points customers to Operations Manager or Azure Monitor. If you move back to Operations Manager on your own servers, the dashboards connect to it. If some workloads move to Azure Monitor, the same dashboards show Azure data next to SCOM.
Talk to us about your SCOM dashboards.
Tell us which SCOM version you run and which service maps and dashboards your teams rely on. We will explain how we would rebuild them and connect your other sources.