Skip to main content

Microsoft Landscape Assessment

Your Microsoft estate, scored across Azure, AI, and data in two weeks.

A fixed-fee assessment of where your Azure foundation, your data platform, and your AI readiness actually stand. You get a readiness score per domain, the gaps that block an AI use case, and a sequenced roadmap to close them.

Fixed fee
€9,500
Duration
2 weeks
Format
Remote-first

At a glance

Fixed fee
€9,500
Duration
2 weeks
Format
Remote-first
Fee credit
Creditable in full within 8 weeks
Markets served
DACH and Benelux

Who it's for

  • You want to put AI into production but you are not sure your Azure foundation and data are ready for it.
  • Your Microsoft estate grew in pieces. Azure, Power BI, and the first AI experiments were each set up by different people at different times.
  • Leadership wants one read of the whole estate before committing to a platform build, not three separate vendor opinions.
  • You have three vendors telling you three different things about your Azure and AI readiness, and no one is scoring them the same way.
  • A board or investor deadline is forcing an AI decision, and you need a fast, defensible read of the platform underneath it.

Scope and format

Two weeks, remote-first, with one optional on-site working session. We assess three domains: your Azure foundation (landing zone, security, cost), your data platform (Fabric, Power BI, and the pipelines feeding it), and your AI readiness (data access, governance, and EU AI Act exposure for the use cases you have in mind). Senior architects do the work. You give us read-only access to the subscriptions and workspaces in scope and one technical point of contact. Where the estate includes SAP, the assessment traces data lineage from the SAP S/4HANA source system through to the semantic model consuming it in Power BI or Fabric.

What you get

Readiness score per domain

Azure foundation, data platform, and AI readiness each scored, so you see which one blocks the others.

The gaps that block AI

The specific foundation and data gaps that would stall an AI use case in production, named and ranked.

EU AI Act exposure read

The use cases you are considering mapped to their likely EU AI Act risk category, before you build anything.

Sequenced roadmap

One roadmap that orders the work: what to fix in the foundation, then the data, then the first use case worth landing.

SAP-to-BI lineage map

Where the estate includes SAP, a traced path from the S/4HANA source tables through to the semantic model that reports on them, with the breaks marked.

Vendor comparison brief

If more than one Microsoft partner has already assessed part of the estate, we reconcile the findings into one scored picture instead of adding a fourth opinion.

Readout session

A working session with your architects and stakeholders to walk the findings and agree where to start.

Pricing

A fixed fee of €9,500. The scope above is the scope, with no day-rate drift.

The full fee is creditable against the AI-Ready Azure Platform engagement if you book it within eight weeks of the readout.

Where your data sits

We work in your tenant with read-only access scoped to the assessment and revoked on completion. No data leaves your environment. Where data residency matters, the assessment covers your landing zone configuration in the Germany West Central Azure region, and we sign your data processing agreement before we start.

Governance & compliance

  • Read-only access, scoped to the assessment and revoked on completion.
  • EU AI Act exposure assessed for the use cases in scope, before any build.
  • GDPR Article 44 data-transfer restrictions checked as part of the Azure foundation review.
  • A signed data processing agreement before kickoff.

Includes EU AI Act positioning and how we classify AI systems.

Read our governance approach

Common questions

How long does it take?

Two weeks, from access granted to the readout session.

How is this different from the Azure Architecture Review?

The Azure Architecture Review goes deep on Azure alone. This assessment reads the whole Microsoft estate, Azure plus data plus AI readiness, and sequences the work across all three. Start here if AI is the goal and you are not sure the foundation is ready.

Do you need production access?

Read-only access to the subscriptions and workspaces in scope. We never need write access for the assessment.

What if we want to do the build with you?

The fee is creditable in full against the AI-Ready Azure Platform engagement if you book within eight weeks. You are not obliged to.

Who actually does the assessment?

The same senior architects who lead every Pavicore engagement, not a delivery team handed off after the sales call. They score the Azure foundation, the data platform, and AI readiness themselves.

What if we only need Power BI or security assessed, not the whole estate?

Take the narrower review instead: the Power BI & Fabric Review or the Cloud Security & Identity Review. This assessment is for when Azure, data, and AI readiness need to be read together because an AI use case is the goal.

Why score all three domains together instead of separately?

Because the gaps interact: a landing zone gap can block a Fabric pipeline, and a data gap can block the AI use case you actually want. Scoring them together is what produces the sequenced roadmap. Three separate reviews would give you three separate opinions and no order of operations.

What if we already have a Cloud Adoption Framework assessment from another partner?

We read it as an input and score against it rather than starting over. The gap, in our experience, is less in the CAF documentation and more in what has drifted since it was written.

Does the assessment include a demo or proof of concept?

No. The assessment scores readiness and sequences the roadmap. Building the first use case is the AI-Ready Azure Platform engagement that follows it.

How is the €9,500 fee justified against three separate reviews?

A separate Azure review, Power BI review, and AI readiness read would cost more individually and still leave the sequencing between them unresolved. This assessment prices the combined read once and delivers the order of operations as part of it.

What happens to the AI Act exposure read if none of our use cases are high-risk?

Then the roadmap says so, and the compliance workload on the build is lighter. We still document the classification, because the "not high-risk" conclusion is itself something an auditor will ask you to show.

Request the assessment