/ One product. Five elements. One supported standard.
We own the result. You accept the standard.
You get a defined system, clear responsibilities, and a product support path. You do not get a private architecture, a named engineer, or an unlimited list of things for Surya to do.
These boundaries do not excuse product failures. Inside the accepted scope, Surya is responsible for restoring the product.
/ Four fit requirements
What acceptance of the standard means.
Supported configuration
The declared scope sits inside the released envelope for identity, endpoints, applications and network.
Required licenses and equipment
The Microsoft licenses and the equipment each released profile needs are in place, on your paper.
Authorized business and data owners
Named people decide access, data permissions and purchasing.
The product change process
Changes to the standard follow the product's change process rather than per-site improvisation.
/ The released envelope
What the standard supports.
The product is built, released and operating. Capabilities and deployment commitments are confirmed for the accepted scope. Released limits are published, and an order is not accepted against a scope outside them.
| Dimension | Supported rule |
|---|---|
| Tenant and identity | A supported Microsoft commercial tenant with an approved identity model, starting with cloud-native Microsoft Entra join. Hybrid and domain-dependent environments complete a separately owned transition first unless a shared hybrid profile is released. |
| Endpoints | Supported Windows hardware and currently supported Windows releases named in the release manifest. Other endpoint operating systems are outside the supported standard. |
| Applications | A versioned catalogue of supported applications, integrations and peripherals. Supported administrative operations belong to the product; application development and vendor defects do not. |
| Network | Approved edge, switch, wireless, segmentation and connectivity profiles. Capacity variants follow tested need, not preference. |
| Sites and geography | Each enrolled site receives its required local recovery arrangement, including its locker. Single-site organizations are not excluded. Installation, field response and replenishment follow a published territory. |
| Capacity | Released maxima for tenants, sites, users, endpoints, applications, network throughput and automation load are being qualified. An unvalidated limit blocks a standard quote rather than becoming an assumed range. |
| Microsoft licensing | Each released profile has a license and control matrix. A capability your licenses do not include is named, not quietly dropped from the baseline. |
| Business ownership | A decision-maker, data and access owners, purchasing authority and a site contact are required. A customer-employed infrastructure operator is not. |
| Existing equipment | Reused only where hardware, firmware, support life, security capability and recovery tests meet the released specification. Otherwise it is replaced. |
| Excluded specialty systems | Servers, arbitrary Azure workloads, industrial control systems, medical devices, custom voice systems and specialized peripherals are not implicitly covered. They require a separately released profile, not a custom statement of work. |
/ Included, your decision, outside
Everyday situations, and who holds them.
| Situation | Included in the product | Your decision | Outside the product |
|---|---|---|---|
| A password or sign-in problem | Handled by the product under the documented recovery path. | You confirm the business authorization for a recovery. | - |
| A new hire or a leaver | The supported technical actions from the standard input and role catalogue. | The employment and access decisions. | A bespoke HR integration, unless a released profile covers it. |
| A Microsoft or carrier outage | Detection, the declared behaviour, and the escalation with a named owner. | Business communication to your own people. | Repair by the vendor or carrier. |
| A business-application error | The supported foundation beneath it, and evidence for the vendor. | Which vendor is engaged and how it is prioritized. | The application's own defects and development. |
| A customer-built AI workflow | The released interfaces, access controls and audit configuration. | The workflow, its authorized actions and its output review. | Workflow development and output accuracy. |
Surya operates the supported product. Business applications, AI workflows, access decisions and data authority stay with your organization.
/ Change management
What happens when the standard is changed.
- Supported changes follow the product's change process: proposed, validated against the release, and applied through the released method.
- When you or a consultant changes the standard, the affected scope is identified, its status is restored or resolved, and the record says which parts are back on the standard.
- A change to one setting does not void every obligation. The affected scope is what changes status.
- You can hire your own consultants at any time. Surya does not become their implementation staff, and they cannot create obligations for Surya.
/ Fit
Where the product fits, and where it does not.
A fit
- A supported Microsoft commercial tenant and an approved identity model
- Supported Windows endpoints and an approved network profile, or willingness to reach them
- Named business, data and purchasing owners, and a site contact
- Acceptance of the released standard and its change process
- Physical sites where a prepared replacement belongs on the wall
Not this release
- A requirement for a private architecture, a named engineer or a bespoke roadmap
- A requirement to keep unsupported equipment, integrations or identity models
- Specialty systems as the core need: servers, industrial control systems, medical devices or custom voice
- Open-ended consulting, staffing or blocks of hours instead of a product
- Technology that cannot be standardized or qualified in this release
The five elements are one product.
Surya Fabric, Surya Workplace, Surya AI Foundation, Surya Control, Surya Standby. Every element is required, and each one has its own acceptance test.