Azure MSP: What a Managed Service Provider Does, and How to Choose One

An Azure MSP (managed service provider) runs part or all of your Microsoft Azure environment on an ongoing contract: monitoring, patching, backup checks, security alerts, cost reports and a support queue for when something breaks. You keep ownership of the subscription, while the provider works through delegated access to response times written into the contract.

This guide comes from Lightray Solutions, which is not an MSP. Edward Pinela, MBA, does project work on Azure, including design, migration planning, cost reviews and reporting, alongside whoever handles your day-to-day support. If you want a second opinion on a proposal or on your environment, the first step is a free 30-minute strategy call; project work is quoted in writing after it.

What does an Azure MSP actually do?

An Azure MSP takes on the recurring operational work that keeps cloud resources healthy, usually for a monthly fee tied to the number of servers, subscriptions or users covered. A sound contract lists which resources are included, the support hours, and how quickly the provider must respond to each severity of incident.

Most providers work in customer environments through Azure Lighthouse, Microsoft's tool for delegated access across tenants. Microsoft's documentation stresses that the customer stays in control: you choose which subscriptions and roles are delegated, you can see the provider's actions in your own activity log, and you can remove the access completely at any time. Lighthouse itself costs nothing extra. Typical scope:

• Monitoring and alerting on virtual machines, databases, storage and networking, with someone on call to respond.
• Patching and backup checks, including test restores rather than a column of green ticks.
• Security operations: reviewing Defender for Cloud alerts, risky sign-ins and policy compliance.
• Cost reporting: monthly spend against budget, idle resources and reservation coverage.
• Changes and incidents handled through a ticket queue with agreed response times.

What is the Azure Expert MSP program, and is it still running?

Azure Expert MSP was Microsoft's top-tier program for managed service providers, and it is closing. Microsoft's Partner Center page says new enrollments stopped on September 15, 2026, renewals end in January 2027, and eligible providers are pointed to a new Frontier Partner specialization instead.

Holding the badge has meant passing an audit at each renewal, which is why buyers treated it as a strong signal, and it still says something about a provider that has it today. After January 2027, though, no provider can renew it, so a missing badge will no longer mean a provider failed to qualify. Ask what each one can show instead: named engineers, written procedures and references from customers of your size.

Do Microsoft credentials on an MSP proposal mean what they seem?

Often less than they seem, because Microsoft credentials come in two kinds. Individual engineers pass role-based exams in their own names. Companies earn Solutions Partner designations, which Microsoft awards at a partner capability score of at least 70 points, combining customer growth, deployments and a skilling count of qualified staff.

A provider can therefore say truthfully that its engineers passed Microsoft exams without the firm holding any designation. Ask which designation the firm holds and in which solution area, and which named engineer on your account passed which exam. A provider that has a designation can show it on its Partner Center membership screen during a video call.

Do you need an MSP or a project-based consultant?

You need an MSP when Azure runs something that must be watched every day and nobody on staff can do it: production servers, a customer-facing application, anything that fails overnight. A consultant fits work with a start and an end, such as designing the environment, planning a migration, reviewing cost or building reports.

Plenty of companies need both, one after the other or side by side. The table shows who usually does what.

What should you ask an Azure MSP before signing?

Ask for every answer in writing, because the contract is where vague promises turn into exclusions. These six questions separate a provider who will run your environment well from one who will simply hold the keys.

• Exactly what is covered? A list of resources, subscriptions and services, and what happens when you add new ones.
• What are the response times? By severity level, and whether they apply at night and at weekends.
• How do you access our tenant? Lighthouse delegation or named accounts, which roles, and whether administrator access is time-limited.
• Who owns what we pay for? Subscriptions, licenses and backups should stay in your company's name, billed to you or itemized.
• How do we leave? Notice period, handover of documentation and scripts, and removal of access on the last day.
• What does the monthly report show? Incidents, changes, patch status, backup test results and cost against budget.

Where does Lightray fit if it is not an MSP?

Lightray does the project work around an MSP contract, not the contract itself. That can mean designing an Azure environment before a provider takes it over, planning a migration, reviewing a proposal or a bill, setting up budgets and cost alerts in Microsoft Cost Management, or building Power BI reports on cloud cost for the finance team.

All of it is delivered remotely by Edward Pinela, MBA, who has 20+ years in technology and 200+ projects behind him; Google reviewers rate Lightray 4.9. Lightray resells nothing, so advice to change provider, plan or design earns it no commission. For the wider service see Microsoft Azure consulting services, Azure cloud migration services and Microsoft 365 consulting.

Further reading: Microsoft Learn — Azure Expert MSP program (retirement notice).