29. 06. 2026
AI, NetEye, Unified Monitoring
30. 06. 2026
Paolo Seghetti
Azure, Cloud, Microsoft, NetEye, NetEye Extension Packs, Unified Monitoring
New NEP Coming Soon: Monitor Your Office 365 Tenant Subscriptions with Confidence
Office 365 is a suite of online subscription services offered by Microsoft as part of the Microsoft 365 ecosystem. It includes capabilities for document creation and management, email, video conferencing, collaboration, and many other productivity services.
The upcoming Neteye Extension Pack (NEP) is designed to monitor subscription-related information within your Office 365 tenant by leveraging the Microsoft Graph API. This makes it possible to collect relevant tenant information and metrics and bring them into NetEye for centralized monitoring and alerting.
Before using the plugin, there are a few important prerequisites to keep in mind. Access to tenant data through Microsoft APIs requires an application to be registered in Azure Active Directory (Azure AD). Since the Office 365 Management APIs and Microsoft Graph rely on Azure AD for secure authentication and authorization, the application must be configured with the proper permissions to access the tenant data that will be monitored.
At a high level, the setup process includes:
- registering an application in Azure AD
- configuring key application properties such as the client ID, reply URL, and tenant access model
- generating a client secret
- configuring an X.509 certificate for secure service-to-service authentication
- assigning the required Office 365 Management API and Microsoft Graph permissions
- requesting access tokens from Azure AD after consent has been granted
To register the application, you need both an Office 365 subscription and an Azure subscription associated with the same Microsoft tenant. Once this prerequisite is in place, the application can be created in Azure AD through the Azure management portal. During registration, the application must be configured with the appropriate sign-on URL and application identifier.
Some application properties are particularly important for this integration:
- Client ID: automatically generated by Azure AD and used for authentication and consent flows
- Multi-tenant setting: must be enabled if the application is intended to access data across tenants after administrator consent
- Reply URL: defines where administrators are redirected after granting consent
The application also requires a client secret, which is generated in Azure AD. Since the secret is shown only once when it is created, it must be stored securely for later use.
For app-only authentication scenarios, an X.509 certificate must also be configured. This involves obtaining a certificate, either self-signed or issued by a trusted certificate authority, and updating the application manifest with the certificate thumbprint and public key.
In addition to the Office 365 Management APIs, the plugin also relies on Microsoft Graph permissions. Depending on the monitoring scope, the application may require the following Microsoft Graph roles:
ServiceMessage.Read.AllServiceHealth.Read.AllReports.Read.AllDirectory.Read.AllUser.Read.AllApplication.Read.All
Once an administrator grants consent, the application can request access tokens from Azure AD and start retrieving the information required for monitoring.
This Microsoft-side setup is the foundation that enables the new NEP to collect subscription-related data and expose it in NetEye in a structured and actionable way.
Keeping control of your tenant subscriptions is one of those tasks that sounds simple — until renewal dates, consumption thresholds, and service continuity all start competing for your attention.
That is why we are excited to share a preview of an upcoming Neteye Extension Pack (NEP) designed to help teams monitor the subscriptions associated with their own tenant in a clear, proactive, and reliable way.
Why subscription monitoring matters
For many organizations, subscriptions are directly tied to business continuity. A missed renewal, an unexpected status change, or a consumption issue can quickly turn from an administrative detail into an operational risk.
With more services becoming subscription-based, IT teams need better visibility into:
- subscription status
- renewal timelines
- usage or entitlement thresholds
- warning conditions that may require action
- potential interruptions before they affect users or services
The upcoming NEP addresses exactly this need by bringing subscription monitoring into the NetEye ecosystem, where observability and actionable alerting already play a central role.
What the new NEP will do
This new plugin is being developed to give administrators an immediate and structured view of the health of their tenant subscriptions.
At a high level, the NEP will allow users to:
- monitor the status of subscriptions linked to their tenant
- detect approaching expiration or renewal deadlines
- highlight anomalous or critical conditions
- integrate subscription checks into existing monitoring workflows
- receive alerts early enough to act before service impact occurs
The goal is simple: turn subscription oversight from a manual, reactive task into an automated and visible monitoring process.
A proactive approach instead of last-minute firefighting
Too often, subscription management becomes visible only when something goes wrong. Teams discover a problem when a service is already degraded, a renewal window has already closed, or internal stakeholders are already asking questions.
By introducing dedicated monitoring for tenant subscriptions, this NEP aims to support a more proactive operating model. Instead of relying on manual calendar reminders or fragmented portals, teams can centralize visibility and react sooner.
In practical terms, that means:
- fewer surprises
- better planning for renewals
- improved operational awareness
- stronger control over service-related administrative dependencies
Designed for real operational workflows
One of the strengths of the NetEye approach is the ability to transform technical checks into operational value. This upcoming NEP follows the same philosophy.
Rather than treating subscription information as something separate from monitoring, it brings it into the same context where teams already track infrastructure, services, and business-critical dependencies.
This makes it easier to:
- correlate subscription risks with operational services
- include subscription checks in dashboards and alerting strategies
- standardize oversight across teams
- reduce the gap between administration and operations
What to expect next
The NEP is currently on its way and will soon provide NetEye users with a practical new capability for keeping tenant subscriptions under control.
We will share more details as the release approaches, including technical highlights, configuration options, and usage examples.
Final thoughts
Subscription-based services are now a core part of modern IT operations. Monitoring them effectively is no longer optional — it is part of maintaining service reliability and operational readiness.
With this upcoming NEP, NetEye continues to expand its monitoring capabilities into areas that matter in everyday operations, helping teams stay informed, proactive, and in control.
Stay tuned for the release.
Why subscription monitoring matters
For many organizations, subscriptions are directly tied to business continuity. A missed renewal, an unexpected status change, or a consumption issue can quickly turn from an administrative detail into an operational risk.
With more services becoming subscription-based, IT teams need better visibility into:
- subscription status
- renewal timelines
- usage or entitlement thresholds
- warning conditions that may require action
- potential interruptions before they affect users or services
The upcoming NEP addresses exactly this need by bringing subscription monitoring into the NetEye ecosystem, where observability and actionable alerting already play a central role.
What the new NEP will do
This new plugin is being developed to give administrators an immediate and structured view of the health of their tenant subscriptions.
At a high level, the NEP will allow users to:
- monitor the status of subscriptions linked to their tenant
- detect approaching expiration or renewal deadlines
- highlight anomalous or critical conditions
- integrate subscription checks into existing monitoring workflows
- receive alerts early enough to act before service impact occurs
The goal is simple: turn subscription oversight from a manual, reactive task into an automated and visible monitoring process.
A proactive approach instead of last-minute firefighting
Too often, subscription management becomes visible only when something goes wrong. Teams discover a problem when a service is already degraded, a renewal window has already closed, or internal stakeholders are already asking questions.
By introducing dedicated monitoring for tenant subscriptions, this NEP aims to support a more proactive operating model. Instead of relying on manual calendar reminders or fragmented portals, teams can centralize visibility and react sooner.
In practical terms, that means:
- fewer surprises
- better planning for renewals
- improved operational awareness
- stronger control over service-related administrative dependencies
Designed for real operational workflows
One of the strengths of the NetEye approach is the ability to transform technical checks into operational value. This upcoming NEP follows the same philosophy.
Rather than treating subscription information as something separate from monitoring, it brings it into the same context where teams already track infrastructure, services, and business-critical dependencies.
This makes it easier to:
- correlate subscription risks with operational services
- include subscription checks in dashboards and alerting strategies
- standardize oversight across teams
- reduce the gap between administration and operations
What to expect next
The NEP is currently on its way and will soon provide NetEye users with a practical new capability for keeping tenant subscriptions under control.
We will share more details as the release approaches, including technical highlights, configuration options, and usage examples.
Final thoughts
Subscription-based services are now a core part of modern IT operations. Monitoring them effectively is no longer optional — it is part of maintaining service reliability and operational readiness.
With this upcoming NEP, NetEye continues to expand its monitoring capabilities into areas that matter in everyday operations, helping teams stay informed, proactive, and in control.
Stay tuned for the release.
Paolo Seghetti
Author
Latest posts by Paolo Seghetti
22. 05. 2026
AI, NetEye, Unified Monitoring
An AI Approach for Old SNMP Devices
30. 03. 2026
NetEye, Unified Monitoring
SNMP and Non-connected Interfaces
28. 12. 2025
Automation, Business Service Monitoring, Icinga Web 2, NetEye, Service Management
Automating Notifications in NetEye
30. 09. 2025
NetEye, Unified Monitoring
Business Process Automation on NetEye