SOC 2 on your stack

SOC 2 with AI on Azure

The short answer

SOC 2 evidence on Azure comes from two places: your Microsoft Entra ID tenant, for identities and sign-in rules, and your Azure subscriptions, for role assignments, logging, keys, network rules, backups and deployments. Each export states its source, command or query, date and record count. An AI assistant can write the read-only queries; your team runs and checks them. Microsoft is a subservice organization in your report, and a licensed CPA firm examines what you provide.

Key takeaways

  • Access evidence has two parts: directory roles in Entra ID and role assignments on Azure resources.
  • Role assignments are inherited from management groups and subscriptions down to resources, so list them at every scope.
  • The assistant drafts queries; a person runs them and sends the output unedited. AI-guided preparation, CPA-performed audit.

What evidence does a SOC 2 auditor ask for on Azure?

Your auditor’s request list sets the exact items; these are the types. The general method is in collect SOC 2 evidence with an AI agent.

SOC 2 evidence on Azure by service area: where the evidence lives and the artifact an auditor asks for.
Service areaMicrosoft servicesArtifact an auditor asks for
Identity and accessMicrosoft Entra ID, Azure role-based access control, Privileged Identity ManagementThe user list, the holders of privileged Entra roles, the Conditional Access policies with their state, and the role assignments at every scope. For selected joiners and leavers, the request and the date access changed.
Logging and monitoringAzure Activity Log, Azure Monitor and Log Analytics, Microsoft Defender for CloudThe diagnostic settings showing where the Activity Log and Entra ID logs are sent, the retention setting, the alert rules, Defender for Cloud status per subscription, and the period’s alerts with the ticket for each.
Encryption and key managementAzure Key Vault; settings of storage accounts and Azure SQLThe listing of vaults with their access model and protection settings, the keys, secrets and certificates with expiry dates (metadata, never values), and the encryption and TLS settings of storage accounts and databases.
NetworkNetwork security groups, Azure Firewall, Application Gateway, Azure PolicyThe listing of network security group rules, with inbound rules open to any address marked, the public IP addresses, the resources open to public network access, and Azure Policy compliance state.
Backups and recoveryAzure Backup, Azure SQL automated backupsBackup policies and protected items, the period’s backup jobs, and the record of a restore test (what, when, by whom, result).
Change and deploymentAzure DevOps or GitHub, ARM or Bicep deployments, Azure Activity LogThe population of production deployments for the period and the branch policy settings. For selected changes, the pull request, review and approval. Activity Log entries for portal changes.

Most support CC6 Logical and Physical Access Controls, CC7 System Operations and CC8 Change Management: see the SOC 2 controls list.

What does Microsoft cover, and what do we cover?

Microsoft describes shared responsibility by service type. With virtual machines you manage the operating system and network controls; with platform services Microsoft operates more of the stack. Whatever the service type, its page says, you keep responsibility for your data, endpoints, accounts and access management. Read Microsoft’s page on shared responsibility in the cloud for the matrix, and SOC 2 on AWS and Azure for what stays with you.

In your report, Microsoft Azure is a subservice organization, normally carved out. Your description names it and the services you use. See subservice organizations: carve-out vs inclusive and vendor management for SOC 2.

Why does Azure evidence come from both the Entra ID tenant and the subscriptions?

Azure has two sets of roles. Entra roles, such as Global Administrator, govern the directory: users, groups and sign-in rules. Azure roles, such as Owner and Contributor, govern resources. They are assigned at a management group, a subscription, a resource group or a resource, and an assignment at a higher scope is inherited by everything below it. A subscription-level export alone leaves out the directory administrators and can leave out what is inherited from a management group.

Start from the subscriptions in scope (see how to scope systems for SOC 2) and write the tenant ID or subscription ID on each artifact. Auditors test such listings for completeness and accuracy before relying on them: see tests of controls, IPE and IUC and audit evidence management best practices.

Which prompts write read-only Azure queries for these exports?

Run the queries yourself under roles that can only read, such as Reader on the subscriptions and Global Reader in Entra ID. Azure Resource Graph suits this work: a query reads configuration across subscriptions and changes nothing. Before you paste output into an assistant, read is it safe to put security documents into ChatGPT or Claude.

Prompt: Entra ID and role assignment listings

You are helping my team prepare SOC 2 access evidence from Microsoft Entra ID and Azure. I will run every command myself under read-only roles.

Ask me first for the subscriptions and management groups in scope, whether we use Privileged Identity Management, and how access is granted and removed today. Wait for my answers.

Then write Azure CLI or Microsoft Graph commands that list: users; members of privileged Entra roles; Conditional Access policies with their state; Azure role assignments at each management group and subscription, including inherited ones. Use only list and show operations. Never write a command that changes configuration or assigns a role. Do not create or alter evidence.

Each command saves its raw output to a file with a header: source (tenant ID or subscription ID), the exact command, date and time in UTC, and record count.

Mark every assumption as [ASSUMPTION].
List anything you assumed that I need to verify.

Prompt: Resource Graph queries across subscriptions

I need read-only Azure Resource Graph queries for a SOC 2 audit, across the subscriptions I name.

Ask me which subscriptions are in scope, which services we run, and what our own policies say about public access and encryption. Wait for my answers.

Then write one query per listing: network security group rules that allow inbound traffic from any address; public IP addresses; storage accounts with their public access and minimum TLS settings. Each result must show subscription ID, resource group and resource name.

Tell me how to save the query text, the run date and the row count with each result, and how to tell whether a result was truncated. Do not create or alter evidence, and do not judge whether a setting is adequate; a person on my team decides. Mark every assumption as [ASSUMPTION].
List anything you assumed that I need to verify.

AI-written policies and descriptions are acceptable only if they describe what your company actually does. The audit tests how controls operate, not how documents read. See what auditors accept from AI.

Who does what

Auditsuisse explains the criteria and sends its evidence request list once engaged. Your management designs and operates the controls; the firm does not configure your tenant or choose your controls.

Who does what when you prepare SOC 2 evidence on Azure.
TaskYour team (with or without AI)Your AI assistantThe auditor
Write export queriesReviews each query before it runsDrafts list commands and Resource Graph queriesNo role
Run the exportsRuns them under read-only roles and keeps the raw outputNeeds no access to your tenantRequests the populations and listings on the evidence request list
Check completenessConfirms the tenant and every subscription are covered and no result was truncatedPoints out missing scopes for a person to resolveTests that each listing is complete and accurate before relying on it
Review privileged rolesDecides whether each role is still neededSorts holders by role and scope for the reviewerInspects the review record and what changed as a result

Frequently asked questions

Do Entra ID and Microsoft 365 belong in the same evidence as Azure?

Entra ID does. It is the directory behind Azure sign-in, so its users, privileged roles and Conditional Access policies are part of your access evidence. Whether Microsoft 365 is in scope is a scoping decision for your management.

Is SOC 2 on Azure different from AWS or Google Cloud?

The model is the same and the service names differ. Compare SOC 2 with AI on AWS and SOC 2 with AI on Google Cloud.

Do we need a compliance platform to collect Azure evidence?

No. A platform connects to Azure and collects these listings continuously. Without one, you run the exports and send them to the auditor. The Zero-Platform SOC 2 audit is built for that, and the guide to SOC 2 with AI covers the rest of the preparation.

Sources & further reading

AICPA, 2017 Trust Services Criteria (with revised points of focus, 2022); SSAE No. 18, AT-C sections 105 and 205. Microsoft, Shared responsibility in the cloud.

Related: SOC 2 with AI on AWS, SOC 2 with AI on Google Cloud, SOC 2 on AWS and Azure.

Product names are trademarks of their owners. Auditsuisse is not affiliated with these vendors.

Sébastien Ruosch

Work with a licensed CPA firm

Auditsuisse Assurance NA PC is a licensed US CPA firm, enrolled in the AICPA Peer Review Program and authorized to perform SOC 2 examinations and issue SOC 2 reports. You prepare; we examine your evidence. See the Zero-Platform SOC 2 audit or book a scoping call.

Back to top ↑