Cybernion
← Insights

IRAP

IRAP for Microsoft Azure: Using the PROTECTED Assessment

3 July 2026 · Updated 5 Sept 2026

Microsoft has had Azure independently assessed against the Australian Government’s Information Security Manual (ISM), with more than 100 services assessed at PROTECTED. That assessment covers the controls Microsoft owns. The system built on Azure, its configuration, identity, data and workload, is a separate scope that must be assessed under IRAP before an agency relies on it.

When an Australian government workload runs on Microsoft Azure, the Azure IRAP assessment is a head start, not the consumer’s assessment. The value is knowing which controls are inherited from Microsoft and which still have to be proven directly.

Is Azure already IRAP assessed at PROTECTED?

Yes. Microsoft has had Azure independently assessed against the ISM, with more than 100 services assessed up to and including PROTECTED, delivered from the Australian regions. Microsoft runs parallel assessments for Azure, Dynamics 365 and Microsoft 365 and refreshes them on a regular cycle, so the in scope list differs by product and moves over time. Check the current reports on the Microsoft Service Trust Portal rather than relying on a fixed count.

There is no IRAP certificate, there is only an IRAP assessment leading to an IRAP report. The Australian Signals Directorate (ASD) retired the Certified Cloud Services List in July 2020 and replaced it with ASD’s Cloud Assessment and Authorisation framework, under which a provider is assessed and each consuming agency makes its own risk based decision. Microsoft’s assessment is an input to that decision. For the fundamentals, see the complete guide to IRAP assessment and is IRAP a certification.

What does the Azure IRAP assessment cover?

It covers the controls Microsoft is responsible for: the physical data centres, the host infrastructure and hypervisor, network and cross domain security, cryptography, access control and the information security risk management behind the in scope services. Those controls are independently assessed against the applicable ISM controls. That assurance is the part a consumer inherits rather than rebuilds.

It does not cover the tenant. How Entra ID is configured, which services are turned on, how the network is segmented, how data is classified and encrypted, and how the workload is monitored are all the consumer’s, and they are where most real world risk lies. That division is the shared responsibility model applied to Azure specifically.

We’re building on Azure. Do we still need our own IRAP assessment?

Yes. Microsoft frames it as security “of” the cloud versus security “in” the cloud. Under the ISM the controls the consumer owns are a separate assessment scope.

Layer Microsoft (assessed) The consumer (assessed separately)
Physical data centres and hardware Yes
Host infrastructure and hypervisor Yes
Service security controls as Microsoft runs them Yes
The consumer’s tenant and service configuration Yes
Entra ID, identity and conditional access Yes
Guest operating systems and patching the consumer manages Yes
The consumer’s data, its classification and encryption choices Yes
The consumer’s application, logging, monitoring and backup Yes

Microsoft states this directly: an entity seeking an approval to operate in line with the ISM can use the Azure IRAP assessment in its own risk assessment, but it is responsible for having its implementation as deployed assessed under IRAP. As per ASD’s Cloud Assessment and Authorisation framework, a Commonwealth entity must have its own system on the cloud assessed, including its shared responsibility obligations.

How do we use the Azure assessment to shorten our own?

Inheritance does the heavy lifting. Confirm the data classification, define the assessment boundary so it captures only the tenant and configuration, then map each applicable ISM control to Microsoft (inherited, evidenced from its assessment) or the consumer (implemented and evidenced in the tenant). The Service Trust Portal guidance helps draw that line for the services in use.

What remains after inheritance is the true scope, and it is smaller and cheaper to assess than a system built from bare infrastructure. In the assessments we run, that remaining scope is usually smaller than the team expects. That is why the platform assessment is worth using well. The same discipline serves SaaS vendors building products on Azure and anyone weighing readiness before the formal assessment. The same inheritance approach applies on AWS and Google Cloud.

Does Azure being assessed at PROTECTED make our workload PROTECTED?

No. PROTECTED is the common bar, and it is set by the sensitivity of the data, confirmed with the owning agency, not by the platform. Azure being assessed at PROTECTED neither raises the workload to PROTECTED nor lowers the bar if the data is OFFICIAL: Sensitive. Settle the classification first, because it decides which ISM controls apply to the scope.

For a PROTECTED workload on Azure that needs the consumer side assessed independently, we provide IRAP assessments and readiness.

Frequently asked questions

Is Microsoft Azure IRAP certified?

There is no IRAP certificate, there is only an IRAP assessment leading to an IRAP report. Microsoft has had Azure independently assessed against the ISM, with services assessed up to PROTECTED. ASD retired the Certified Cloud Services List in 2020, so no provider is IRAP certified. The assessment supports the customer’s own risk decision, it does not grant an approval.

We’re building on Azure. Do we still need our own IRAP assessment?

Yes. Microsoft’s assessment covers the controls Microsoft owns. The system built on Azure, its configuration, identity, data and workload, is a separate scope that must be assessed under IRAP before an agency relies on it.

Does the Azure IRAP assessment cover Microsoft 365 too?

Microsoft runs separate IRAP assessments for Azure, Dynamics 365 and Microsoft 365. Check the Service Trust Portal for the current in scope services in each assessment, because coverage differs by product and changes each cycle.

Where do we download the Azure IRAP assessment?

The Azure IRAP assessment reports and supporting guidance are on the Microsoft Service Trust Portal, in the Australia IRAP section. Access requires a signed in Microsoft account with the appropriate agreement.

Can we reuse Microsoft’s Azure assessment in our own?

In part. A consumer can inherit the controls Microsoft owns and reference its assessment in the risk assessment. A separate IRAP assessment is still needed of the controls the consumer owns under the shared responsibility model, evaluated as deployed.


Written by Gaurav Vikash, an ASD endorsed IRAP assessor and senior cyber security leader with 18 years of experience across Australia, the UK and Asia, including CISO and senior security leadership roles. He holds CISSP, CISA, CISM and CRISC and is an ISO 27001 Lead Auditor and ISO 42001 Lead Implementer, and speaks regularly at industry conferences.

Talk to us.

Sources:

  1. Australia IRAP, Azure compliance, Microsoft, learn.microsoft.com, 2026
  2. Australian Government IRAP, Microsoft compliance, learn.microsoft.com, 2026
  3. Cloud assessment and authorisation, ASD, cyber.gov.au, 2025
  4. Cloud services, IRAP, ASD, cyber.gov.au, 2025
  5. Information Security Manual, cyber.gov.au, June 2026
  6. Service counts are point in time and change each assessment cycle; the current list is on the Microsoft Service Trust Portal

Last updated: 5 September, 2026

Related serviceIRAP AssessmentSee the service →

Talk to us about your engagement

A scoped proposal within one business day.