Services
Operations for Azure and Microsoft 365.
Entria operates Azure resources and Microsoft 365 environments alongside your IT team. Explore what each service covers and how we work.
Per resource
Managed Azure operations
Choose the Azure resources and service level that fit your environment. Billing is per resource, for each day it is in scope.
What each level coversPer user
Microsoft 365, Entra and Intune
Choose from three packages for Microsoft 365, Entra and Intune. Each builds on the previous package and is billed per user per month.
What each package addsPer resource
Managed Azure operations.
Add OperatedBy:Entria to the supported resources you want us to operate, or to their resource group. Use the ServiceLevel tag to select Basic, Standard or Premium.
| Capability | Basic | Standard Default | Premium |
|---|---|---|---|
| Patch management | Included | Included | Included |
| Backup administration | Included | Included | Included |
| Incident management | Failed patch or backup only | Included | Included |
| Monitoring and alerting | Not included | Included | Included |
| Baseline enforcement | Not included | Included | Included |
| Capacity management | Not included | Included | Included |
| Monthly report | Not included | Included | Included |
| Coverage | 08–16 | 08–16 | 08–16, and 24/7 on P1 and P2 |
A resource can inherit its ServiceLevel from its resource group. A non-empty tag on the resource takes precedence. Standard is the default when neither has a value. Basic is available for resource types where patching and backup apply.
Coverage
Incident coverage.
Incidents are prioritised by impact, and coverage depends on the service level.
Incident priorities
- P1 · Critical
- A production outage, for example, may be treated as P1.
- P2 · High
- A severely degraded service may be treated as P2.
We work on P1 and P2 incidents continuously until they are resolved or downgraded.
Coverage by service level
- Basic and Standard
- Coverage during working hours.
- Premium
- Working-hours coverage, with around-the-clock coverage for P1 and P2 incidents.
Basic incident management covers failed patching and backups.
Scope
The Azure resources we operate.
The resources below are covered by our Azure operations service. The service level determines which checks and operational tasks apply.
- Virtual machines
- Azure SQL1
- Azure Virtual Desktop
- Azure Firewall
- App Service
- Storage accounts
- VNet gateways
- PostgreSQL flexible servers
- MySQL flexible servers
- Key vaults
- Virtual networks and NSGs
- Public IPs
- Load balancers
- Recovery Services vaults
- Log Analytics workspaces
- Bastion
1 Azure SQL is counted as one type and covers SQL servers, SQL databases, elastic pools and SQL managed instances.
Supporting resources
Managed disks, DNS zones and route tables are covered as part of the resource they support. The Azure Update Manager and Azure Monitor configurations used to operate it are also included.
Unsupported resources
If we find a tagged resource type that we don't operate, we'll contact you.
Per user
Microsoft 365, Entra and Intune.
Compare the packages below. Each is billed per user per month.
| Capability | Entria Core | Entria Business | Entria Enterprise |
|---|---|---|---|
| Tenant and identity administration Tenant management, MFA, self-service password reset, user and group administration in Entra ID, and a tenant baseline through Maester | Included | Included | Included |
| Backup Exchange, SharePoint and OneDrive | Included | Included | Included |
| Entra ID signal monitoring Risky sign-ins, user risk and sign-in anomalies, with incident management on them | Included | Included | Included |
| Monthly status report | Included | Included | Included |
| Conditional Access With monitoring of its sign-in impact | Not included | Included | Included |
| Device management Intune security baselines, Autopilot, Windows Update rings and compliance policies | Not included | Included | Included |
| Threat detection and posture Defender for Endpoint, Microsoft Sentinel with standardised analytics rules, and Secure Score tracking with quarterly recommendations | Not included | Included | Included |
| Automated joiner and leaver administration | Not included | Included | Included |
| Quarterly review Security, spend, and what we would change | Not included | Included | Included |
| Microsoft Copilot Deployment, adoption support and governance | Not included | Not included | Included |
| Data governance Microsoft Purview for DLP policies, sensitivity labels and data classification | Not included | Not included | Included |
| Extended Sentinel Hunting queries and behavioural analysis | Not included | Not included | Included |
| Half-yearly security assessment | Not included | Not included | Included |
Security and access
Access to your Azure environment.
For Azure operations, Entria uses two applications in your Entra ID. Discovery reads your environment; Operations makes changes within the permissions you grant. You control access to both applications.
Entria Discovery Reader
Discovers resources and checks their configuration. It has read-only access and cannot make changes.
Entria Operations Contributor
Reads configuration and makes operational changes within its assigned permissions.
- Control over changes
- Disable Entria Operations to stop changes through that application. Discovery can continue to read while its access remains enabled.
- Azure Activity Log
- Both appear under Enterprise Applications in your portal. Azure management changes made through Entria Operations appear in your Activity Log.
- Federated credentials
- The two applications use federated credentials instead of client secrets.
- Role assignments
- Your team assigns and controls the applications' Azure roles. We agree the required access during onboarding.
FAQ
Common questions.
- Are we bound by a long contract?
- No. You can cancel with one month's notice to the end of a month. For example, notice given on 27 October ends the agreement on 30 November.
- What do we need to do to get started?
- Approve the two applications and assign their Azure roles. We agree the scope and baselines with you before operations begin.
- Where do you store data about our environment?
- In an Azure database hosted in the EU.
- What happens if we want to stop?
- At the end of the agreement, we provide a report on the resources we operated and their status.
- How is it priced?
- You receive a monthly invoice. Azure resources are charged for each day they are in scope; Microsoft 365 is charged per user per month. After the Azure review, you receive a quote for your environment.
Let's look at your Azure together
-
01
A short intro call No access
Tell us about your Azure environment and what you need help with. No obligation.
-
02
A free Azure review Read-only
With read-only access, we look at your environment and share what we find.
-
03
Your report and a quote Yours to keep
You get a findings report and a quote for your environment. The choice is yours.
-
@
Or write to us
Received
We'll come back to you within one working day.
You get one email with a proposed time for the call. Nothing happens in your environment until you have approved it.