Architecture, Engineering and Construction
Project data, external teams, and a tenant that has to hold both.
An AEC firm runs most of its work with people who do not work for it. Consultants, contractors, subcontractors, and client teams all need access to live project material, often for the length of one project and no longer. That is a guest identity and data boundary problem before it is anything else.
What is already true here
- Project teams that cross company boundaries by default
- Large design and model files that resist ordinary collaboration patterns
- Joint ventures that need a shared workspace with a defined end date
- Guest access that accumulates across projects and is rarely removed
- Site and field staff working from mobile devices on poor connections
- Contractual obligations about where project information is held
What we do about it
- External collaboration design in Entra, with review and expiry on guest access
- Project workspace structure that can be archived cleanly at handover
- Sensitivity labeling for commercially confidential design material
- Conditional Access that fits how site teams actually work
- Readiness review before AI tooling is pointed at project content
On what this page claims
Everything above describes conditions that are true of Architecture, Engineering and Construction before we are involved. None of it asserts that we have served a named customer in this sector. Where we have customer evidence it is published separately, with the class of evidence stated alongside it.