Limitations, Dependencies, and Prerequisites
This section sets out the platform-level boundaries, dependencies, and prerequisites that apply across the services. Each service also states its own specific requirements and exclusions in its service description.
At a glance
- Delivery
- SaaS only; no on-premises platform installation
- Depends on
- Customer Cisco and Microsoft infrastructure, per service
- Boundaries
- Access is bounded by the tenant model
- Roadmap
- Planned capabilities are marked and not part of the service until released
Delivery model
Section titled “Delivery model”The platform is delivered only as a SaaS. There is no on-premises installation of the platform itself. Where a service integrates with on-premises equipment, that equipment remains the customer’s to operate. For example, Endpoint Manager works alongside an existing on-premises Cisco ISE deployment; it does not replace or host ISE.
Customer-provided prerequisites
Section titled “Customer-provided prerequisites”The services integrate with infrastructure the customer already runs. Depending on the services chosen, prerequisites include:
- Supported Cisco wireless or network equipment (Cisco Meraki, or a Cisco router acting as a service gateway).
- For Endpoint Manager, a reachable Cisco ISE deployment with the required APIs enabled.
- For certificate-based EntryPoint authentication, an identity source such as Microsoft Entra ID, and Microsoft Intune where device compliance is required.
- Appropriate network connectivity, as set out in Network Requirements.
Dependencies during operation
Section titled “Dependencies during operation”Some services depend on the availability of customer-side systems. Endpoint Manager, for instance, depends on reachability to Cisco ISE; while ISE is unreachable, endpoint operations cannot complete, and the condition is recorded in the audit trail.
Multi-tenant boundaries
Section titled “Multi-tenant boundaries”Access is bounded by the tenant model. An identity sees only the organizations and contexts where it holds a role, and the boundary between organizations is absolute. See Tenant and Organization Structure.
Availability of capabilities
Section titled “Availability of capabilities”The service descriptions distinguish between capabilities available today and capabilities that are planned. Planned capabilities are marked as such and are not part of the service until released.
Acceptable use
Section titled “Acceptable use”Use of the platform is subject to the acceptable-use provisions of the Service Terms, including not impeding the security, stability, or availability of the service.
Related sections
Section titled “Related sections”- Network Requirements: the connectivity prerequisites.
- Support and Responsibility Allocation: service level exclusions.