Your administrators authorize every source.
You authorize purpose, population, resources, time, retention and Microsoft permissions. Teams, SharePoint Online, Exchange Online and Entra are mandatory together for first live qualification. You do not need to identify valuable workflows or files in advance; IIC discovers the work within that boundary. Where Microsoft offers scoped access, such as selected SharePoint sites, scoped Exchange application access, and resource-specific consent for Teams, the scope is used. Your administrators can withdraw a source or a permission at any time.
A filter inside an application is not a substitute for the correct Microsoft access boundary. Both are reviewed. Signing in to the Launchpad does not grant Azure administration, authorize Microsoft evidence, or approve model spending.
Discovery is read-only.
IIC reads the sources you authorize. It does not send messages, change files, or act in your systems during discovery. An engineering Build Pack is a handoff for an engineer. It does not implement the capability or authorize production action.
IIC looks at work, not at people’s performance.
IIC reconstructs how work moves across people and systems so that machine burden can move away from the people carrying it. It is not an employee monitoring or performance product. It is not used to rank, score, reward, or discipline individuals.
Installation uses your own execution context.
The Launchpad is not a remote cloud administrator. It prepares your installation package and instructions. Your Azure administrator runs one guided step in Azure Cloud Shell, signed in as themselves, and performs the Microsoft administrator approvals. Your Workbench authenticates independently of the Launchpad. A Launchpad sign-in is never forwarded to it.
Processing boundaries are specific.
Customer hosting does not mean every processing step stays inside one tenant. Microsoft 365 and the Azure OpenAI deployment you select have their own processing boundaries. Optional installation status sharing sends only permitted deployment metadata. Residency, classification, and contractual requirements are established for your actual deployment, not assumed from the cloud logo.
What we do not claim.
No compliance certification is claimed or implied. IIC is offered through founder-guided customer-owned installation and discovery. No live customer deployment, accuracy result, or realized saving is established by this website.
One installed discovery product.
Every assessment begins with guided installation and authorized Microsoft discovery. A consulting-only assessment or supplied evidence package cannot replace or supplement that product route. Internal engineering fixtures and outbound customer handback remain distinct; neither establishes live qualification.
Operating ownership comes before handoff.
Agree who handles hosting, exceptions, recovery, security and model changes, and maintenance. Customer-maintained operation and separately scoped support are options to discuss. No automatic support coverage is implied.
What this website collects.
Inquiry forms collect business contact details and high-level context. They do not connect your Microsoft environment, accept operational evidence, or run IIC. Please leave out customer records, credentials, payroll, and confidential documents.