Deployment
Deploying Kybera Impact is a scripted, repeatable, phased rollout into your Microsoft 365 tenant and Azure subscription. Every phase is automated — not a manual consulting exercise. That's what makes deployments fast, consistent, and auditable.
The phases
- Azure infrastructure — automation accounts, managed identities, key vault, storage. Deployed into your Azure subscription.
- Power Platform environment — DLP policy, connection references, environment readiness for the Kybera Impact solution.
- The Kybera Impact portal — a SharePoint site with the workspace registry, templates store, workflow queue, and configuration lists. Scripted into existence.
- The IM model — enterprise content types, site columns, bilingual taxonomy, hub structure, Business Authority hierarchy. Deployed in one scripted pass, supported by an IM working session to align the content-type model with your organization's needs.
- Templates and catalogue — workspace and library templates built from reference sites your IM team configures, then exported and published into the catalogue.
- Organization onboarding — bulk provisioning of your initial hub-and-spoke structure. Your organization is Kybera Impact-managed from day one rather than growing into governance site-by-site.
Client and provider responsibilities
A typical allocation:
| Area | Client | Provider |
|---|---|---|
| Tenant and subscription access | Provides | Uses only as needed |
| Information architecture decisions | Provides business input | Scripts the deployment |
| Reference sites | Provides reference sites configured as desired | Generates templates |
| Approval model | Decides broker structure and scope | Configures portal roles |
| Bulk onboarding | Provides organizational structure | Runs bulk provisioning |
The provider takes responsibility for the platform's correct deployment; your organization takes responsibility for the decisions the platform reflects.
Why scripted matters
- Repeatable. The same scripts run the same way across environments and customers.
- Rerunnable. Idempotent where possible — running a script twice doesn't break what already exists.
- Versioned. Deployment artefacts under source control. Every change is tracked.
- Auditable. Your security reviewers can inspect what the deployment will do before it runs.
- Faster. What takes days manually typically takes hours scripted.
- Consistent. The Kybera Impact in your tenant is the same Kybera Impact in every other client's tenant — which is what makes "supported product" meaningful.
After deployment
Compliance and audit run daily. Tenant reconciliation and disposed cleanup run monthly. Your IM team adds templates and taxonomy terms through the IM Portal. Brokers approve requests as they come in. Your governance forum reviews Insights dashboards on whatever cadence works for you. There are no manual artefacts that need re-running.
Where this fits
How it's built covers the architecture this deployment installs. Security & tenant boundaries covers what your security review evaluates during deployment.