Strategic Briefing

DORA put your Microsoft contract on the regulator's desk.

For financial entities in scope of the Digital Operational Resilience Act, Microsoft is no longer just a vendor. It is a critical third party whose contract terms, exit provisions, and concentration profile are now matters of regulatory attention. DORA prescribes what an outsourcing contract with a critical ICT provider must contain, and a standard Microsoft agreement does not contain it by default. The gap between what DORA requires and what your EA says is a gap the practice closes at renewal, not in an audit response. This briefing names how a Microsoft agreement is brought into DORA alignment without paying a premium for the privilege.

Speak with the practice Financial services practice →
Why DORA is a contract issue

Resilience is regulated. The contract is the evidence.

DORA holds financial entities accountable for the operational resilience of their critical ICT providers, and it specifies the contractual provisions an arrangement with such a provider must include. Access and audit rights, exit strategies, subcontracting transparency, incident cooperation, and service level commitments are no longer optional contract hygiene. They are the documentary evidence a regulator examines. A Microsoft EA written before DORA was a commercial concern rarely contains these provisions in the form the regulation expects. The practice treats the DORA gap as a renewal deliverable, mapping the required provisions against the existing agreement and negotiating the difference into the contract as part of the renewal rather than as a costly mid term amendment under regulatory deadline.

Five DORA provisions

What the agreement must contain.

Provision 01
Exit strategy

A documented, executable exit.

DORA expects a financial entity to have a viable exit strategy for a critical ICT provider, which means the Microsoft agreement must support an orderly transition rather than obstruct it. The practice negotiates the exit provisions, transition assistance, and data return terms into the agreement so the exit strategy on paper is executable in practice.

Provision 02
Audit and access

Access, inspection, and audit rights.

DORA requires access and audit rights for the entity and its regulators over a critical provider. The practice ensures the agreement grants these rights in the scope the regulation expects, including the ability for the competent authority to exercise them, rather than the narrower audit language a standard agreement offers.

Provision 03

Subcontracting transparency.

DORA expects visibility into the chain of subcontractors supporting a critical service. The practice negotiates subcontracting disclosure and the right to object into the agreement so the resilience picture extends through the provider's own supply chain.

Provision 04

Incident cooperation and reporting.

The entity's own incident reporting obligations depend on cooperation from the provider. The practice writes incident notification, cooperation, and information sharing terms into the agreement so the provider's obligations support the entity's regulatory reporting timeline.

Provision 05
Concentration

Managing the concentration risk the regulator now watches.

DORA brings ICT concentration risk into supervisory view, and a financial entity heavily dependent on a single provider across M365, Azure, identity, and security carries a concentration profile a regulator may question. This is a strategic licensing decision, not only a contract clause. The practice maps the Microsoft concentration across the estate, frames the resilience and exit posture that addresses it, and ensures the renewal does not deepen a concentration the entity will have to defend. The contract provisions satisfy the examiner. The concentration strategy satisfies the supervisor.

The alignment program

Closing the DORA gap at the renewal.

The DORA provisions are cheapest to secure at renewal, when the whole agreement is open, and most expensive to secure mid term under a supervisory deadline. The five step program below closes the gap on the renewal calendar rather than the regulator's.

Step 01
Classify the arrangement. Confirm which Microsoft services support critical or important functions under DORA, because the contractual obligations attach to those functions specifically. Not every line of the estate carries the same requirement.
Step 02
Gap the existing agreement. Map the DORA required provisions against the current EA and identify exactly where the agreement falls short on exit, audit, subcontracting, and incident terms.
Step 03
Draft the provisions. Convert each gap into specific contract language with the scope and specificity the regulation expects, rather than generic resilience wording that an examiner will reject.
Step 04
Map the concentration. Assess the Microsoft concentration across the estate and frame the exit and resilience posture that addresses the supervisory concern, so the renewal does not deepen an exposure the entity must later defend.
Step 05
Negotiate at renewal. Fold the DORA provisions into the renewal so they are secured as part of the commercial negotiation rather than purchased as a premium amendment under deadline pressure.
What the program produces

The outcomes a DORA aligned agreement delivers.

Outcome 01

An exit strategy that holds up.

The agreement supports an orderly, executable exit, satisfying the DORA expectation that a critical provider arrangement can be unwound without disrupting a critical function.

Outcome 02

Audit rights at regulatory scope.

Access, inspection, and audit rights extend to the entity and its competent authority in the form DORA expects, rather than the narrower terms of a standard agreement.

Outcome 03

Concentration risk framed and addressed.

The Microsoft concentration is mapped and the resilience posture is documented, so the entity can answer a supervisory question rather than discover the exposure during one.

Outcome 04

Provisions secured without premium.

The DORA provisions are negotiated into the renewal as part of the commercial deal rather than bought as an amendment under deadline, avoiding the premium a late request invites.

Close the DORA gap on your renewal calendar.

The practice supports financial entities on bringing the Microsoft agreement into DORA alignment, drafting the required exit, audit, subcontracting, and incident provisions, and managing the concentration risk the supervisor now watches.

Related work

Where this connects.