Cloud infrastructure documentation for the IT you no longer see
Many small and mid-sized firms now run much of their IT in Microsoft 365, Azure, AWS and SaaS applications rather than in their own server closet, yet their documentation still describes the office network. Cloud infrastructure documentation records how those environments are actually configured: which domains the tenant owns, which Conditional Access policies apply to whom, who holds admin roles, how mail is authenticated, which virtual networks exist and what is reachable from the internet.
Cloud settings change in a web portal with a few clicks, often without a ticket. A change made by a former MSP or a vendor’s support engineer stays invisible until something breaks or an auditor asks. A written record, with dates and owners, makes those portals reviewable again.
OC Security Audit builds and audits this record for firms in Irvine, across Orange County and Southern California, and remotely for clients nationwide. Discovery uses read-only access. We document your settings; we do not change them.

What the Microsoft 365 tenant record covers
The tenant is where identity, mail and files meet. These are the settings we record.
| Area | What we document | Why it matters |
|---|---|---|
| Tenant and domains | Tenant ID, the .onmicrosoft.com domain, every verified custom domain, registrar and DNS host, domain renewal dates | An expired domain or a lost registrar login can take mail down for everyone. |
| Conditional Access | Each policy’s name, state (on, off or report-only), included and excluded users and groups, target apps, conditions and grant controls | Exclusions are where gaps hide. A report-only policy does not block anything. |
| Admin roles and PIM | Who holds Global Administrator and other privileged roles, permanent versus eligible assignments, activation rules and approvers | Every standing admin assignment is an account worth protecting first. |
| Break-glass accounts | Account names and vault references (never passwords), sign-in method, Conditional Access exclusions, alerting, last validation date | They are the way back in when every other admin login fails. |
| App registrations | Application name, owner, API permissions, admin consent, client secret and certificate expiry dates | Apps keep their access after the person who added them leaves, and an expired secret breaks an integration without warning. |
| Exchange Online mail flow | Accepted domains, connectors, transport rules, external forwarding settings, and the published SPF, DKIM and DMARC records | Connectors, rules and forwarding decide where your mail can go. |
| SharePoint and OneDrive sharing | Tenant-level external sharing level, site-level exceptions, guest access and the default sharing link type | These settings decide whether a link can reach someone outside the company. |
The full review of these settings against good practice is a separate engagement: see the Microsoft 365 full security audit and the Microsoft Entra ID security audit. The record described here is what those audits compare against.
Subscriptions, networks and the controls around them
Azure and AWS need the same rigor as a server room: what exists, how it connects and who can reach it.
Azure structure
Management groups, subscriptions and resource groups, with naming conventions, tags, owners, billing contacts and the Azure Policy assignments applied at each level.
Azure networking
Virtual networks and subnets with address ranges, peerings, network security groups with the business reason for each rule, VPN gateways with their on-premises peers, and public IP addresses.
Key Vault and backup
Which key vaults exist, who can access them, and the names and expiry dates of certificates and secrets (never their values). Recovery Services vaults, backup policies and retention.
AWS accounts
Accounts and organization structure, VPCs and subnets with CIDR ranges, security groups and their rules, IAM roles and who can assume them, and root account protection.
Address ranges in Azure and AWS belong in the same plan as your office subnets, so a new VPN or peering never overlaps an existing network. See IP address and VLAN documentation. For a security review of the subscription itself, see the Azure cloud security audit.
Sample tenant settings record
- Tenant
- harborviewdental.onmicrosoft.com · primary domain harborview.example
- Snapshot
- 2026-10-01, compared with 2026-09-01
- Conditional Access
- 6 policies: 5 on, 1 report-only (CA05 Require compliant device for admin portals)
- Global Administrator
- 4 assignments: 2 break-glass accounts (permanent active), 1 named admin (eligible through PIM), 1 added since the last snapshot with no change record
- Break-glass
- bg-admin@harborview.example · vault reference VLT-0007 · FIDO2 key · last validated 2026-09-12 · finding: uses the custom domain, not .onmicrosoft.com
- Mail authentication
- SPF published · DKIM enabled for harborview.example · DMARC p=none (monitoring only)
- App registrations
- 4 apps · Imaging-Sync client secret expires 2026-10-25 · 1 app has no recorded owner
| Change since last snapshot | Before | After | Change record |
|---|---|---|---|
| Conditional Access CA05 | Not present | Report-only | CHG-0142, approved |
| External sharing, site Referrals | Existing guests | Anyone | None found (finding) |
| Global Administrator assignments | 3 | 4 | None found (finding) |
| DMARC policy | p=none | p=none | No change |
Every difference either matches an approved change record or becomes a finding. That is the link between this record and IT change management: the snapshot shows what changed, the change record shows that someone meant it to.
Point-in-time snapshots that show drift
Export
Capture the configuration on a set date with export tools rather than screenshots, so the record is complete and repeatable.
Store
Keep each dated export with the documentation, protected like the rest of it.
Compare
Compare the new export with the previous one. Only the differences need a human to read them.
Reconcile
Match each difference to a change record. Unexplained changes go on the findings list with an owner.
Document emergency access accounts the way Microsoft describes them
Microsoft’s guidance on emergency access accounts in Entra ID gives you a clear list of facts to record and check.
- Two or more emergency access accounts, so one lost key does not lock you out
- Cloud-only accounts on the .onmicrosoft.com domain, not synchronized or federated from on-premises
- Excluded from Conditional Access policies that block or restrict sign-in
- Phishing-resistant sign-in (FIDO2 passkey or certificate-based authentication), different from your normal admin accounts
- An alert on every sign-in, sent to more than one administrator
- Validated at least every 90 days and after a change in IT staff, with the date written down
The documentation holds the account names, the location of the keys and a reference to the vault entry. The secret itself never appears in a document. See IT password documentation for how that reference works.
The SaaS applications nobody listed
Practice-management, payroll, e-signature and imaging systems often hold the most sensitive data, and they rarely appear in IT documentation.
For each SaaS application we record its business purpose and owner, the people with admin rights, how users sign in (single sign-on through Entra ID or a separate login with a vault reference), the type of data it stores, license count and renewal date, vendor support contacts, and how you would get your data out if you left.
NIST CSF 2.0 calls for inventories of software, services and systems (ID.AM-02) and of services provided by suppliers (ID.AM-04). The SaaS list feeds your IT asset inventory, and any application that stores patient, card or taxpayer data appears on your data-flow diagrams.
Build the cloud record, or audit the one you have
The IT Documentation Build includes a cloud settings record for Microsoft 365, Entra ID, Azure and AWS, delivered in your own documentation platform or in our encrypted documentation package. The IT Documentation Audit scores the cloud records you already keep against all 13 documentation domains and gives you a prioritized roadmap.
Both packages are $3,500 fixed, one-time. Scope is confirmed on a 30-minute call. See the IT documentation audit or the IT documentation pricing for what each includes. If you want someone to fix what the record uncovers, our implementation partner IT Perfection can do the hands-on work.

Where to go next
IT change management
How to make every cloud and network change requested, approved, tested and recorded.
Data-flow diagrams
Show where patient, card and taxpayer data travels between your office, cloud and vendors.
Page 8 of 22: Cloud documentation: Microsoft 365, Azure, AWS
- 1. IT documentation services (hub)
- 2. Why IT documentation matters
- 3. What to include in IT documentation
- 4. Network documentation
- 5. IP address and VLAN documentation
- 6. WAN and ISP circuit documentation
- 7. Firewall and network settings documentation
- 8. Cloud documentation: Microsoft 365, Azure, AWS (this page)
- 9. Data-flow diagrams
- 10. IT asset inventory
- 11. IT password documentation
- 12. IT change management
- 13. Runbooks and disaster-recovery documentation
- 14. Securing your IT documentation
- 15. IT documentation for compliance
- 16. IT documentation software compared
- 17. Configuration backup and change tools
- 18. How to document a network
- 19. IT documentation checklist
- 20. Sample IT documentation package
- 21. IT documentation audit
- 22. IT documentation pricing

Guided by Ali Hassani, CISO
Certified CISO (C|CISO) and CISSP with 25+ years in IT, cybersecurity, compliance and infrastructure, and dozens of Microsoft and Cisco certifications, including MCSE, MCITP, MCSA Security, CCNP and CCNA. Ali reviews a cloud tenant the way he reviews a firewall: setting by setting, with the business reason written next to every exception.
Cloud documentation questions
Do you need Global Administrator access to document our tenant?
No. In most tenants, read-only roles such as Global Reader and Security Reader in Microsoft 365, Reader in Azure and read-only policies in AWS are enough. We confirm the exact access on the scoping call.
Is this the same as a Microsoft 365 security audit?
No. Documentation records what is configured and why. A security audit judges those settings against good practice and ranks the risks. Having the record first makes the audit faster.
Will the documentation contain our secrets or keys?
No. We record the names, owners and expiry dates of secrets and certificates. The values stay in Azure Key Vault or your password vault.
Our MSP manages the tenant. Can you still document it?
Yes, with read-only access granted by the tenant owner. The finished record belongs to your company, not to us and not to the MSP.
How often should the cloud record be refreshed?
We suggest a fresh snapshot at least each quarter and after any significant change, such as a new Conditional Access policy or a new subscription. Quarterly review can be part of our vCISO service.
Implementation partner
OC Security Audit documents and audits; it stays independent of the administration of your systems. If you want hands-on work, IT Perfection can fix what the documentation uncovers and keep the records current as part of managed IT.

Get your cloud settings on record before someone asks for them
Tell us which tenants, subscriptions and accounts you run, and we will scope the record with you. Schedule a consultation.
Irvine, Orange County and Southern California on-site; remote nationwide. Fixed one-time price: $3,500.


