Path to first architecture proof
- Create an organisation and project.
- Grant Reader at subscription scope to the C4CI platform identity.
- Verify access, run scan, then review the generated C4 view.
Quickstart steps
1. Sign in and create an organisation
availableUse an email, Microsoft, Google, or GitHub login. Your organisation is the billing and access boundary for projects and team members.
2. Create a project
availableCreate one project for the Azure subscription you want to inspect. Use a clear name such as production, platform, or client environment.
3. Connect Azure with Reader role
availableGrant Reader role at subscription scope to the C4CI platform identity shown in the project connection panel. Do not grant Contributor or Owner for discovery.
4. Verify the connection
availableReturn to C4CI and verify access. If Azure RBAC propagation is still catching up, wait a few minutes and retry before changing permissions.
5. Run the first scan
availableRun discovery from the project page. Typical subscriptions finish quickly; larger estates can take longer because scan time follows resource count and API response time.
6. Review diagrams and proof state
guided rolloutOpen the generated architecture view. L1/L2 validation starts on Free. Deeper diagram levels, drift, exports, and governance features follow the pricing and proof-state labels shown in the product.
Tier boundaries in this guide
| Tier | Public quickstart claim | Proof state |
|---|---|---|
| Free | One Azure subscription and L1/L2 validation. | available |
| Pro | Deeper architecture workspace, drift, exports, and AKS views. | guided rollout |
| Enterprise | Governance-heavy workflows and compliance reports. | pilot |
| PAYG | Itemized consultant-slice usage for billable actions. | guided rollout |
The phrase live-proof pending means implementation or route support exists, but public readiness evidence is not yet strong enough for a live-proven claim.