- Graphwise Platform Documentation
- Graphwise Integrations
- Introduction to Graphwise for Microsoft 365
- M365 Connectors Deployment Overview
- Deployment Responsibilities and Considerations
Deployment Responsibilities and Considerations
13/08/2026
Connectors 1.1 // GW4M365
This section describes the responsibilities of the customer and implementation team, along with the security and operational considerations that should be addressed before and during deployment.
The following responsibilities help ensure that all parties understand their roles and obligations throughout the deployment process.
Customer Responsibilities | Graphwise Responsibilities |
|---|---|
Provide access to the SharePoint tenant, target site and App Catalog. | Provide the approved connector release package and applicable documentation. |
Provide or approve the required administrative permission during deployment. | Provide environment-specific configuration guidance. |
Approve Microsoft Entra ID application registrations and permissions. | Deploy or support deployment of the Graphwise Platform according to the agreed model. |
Provide applicable network, security, compliance, DNS and certificate requirements. | Configure the connector and required integration workflows. |
Complete customer-controlled identify, firewall and infrastructure actions. | Support testing, troubleshooting and issue resolution during implementation. |
Participate in validation and acceptance. | Provide release-specific known limitations and operational guidance. |
Review the following security and operational considerations before deployment to ensure the solution is implemented, managed and maintained in accordance with organizational requirements and best practices.
Ensure credentials, secrets, licence files and customer-specific configuration are delivered through an approved secure channel.
Administrative access should be time-bound where possible and reviewed after deployment.
Ensure that the final production design addresses resilience, scalability, backup, monitoring, logging, and recovery requirements.
Network routes, allowed origins, redirect URIs, and external endpoints must be approved by the customer security team.
The connector must operate within the customer SharePoint and Microsoft Entra ID governance policies.
Review release-specific limitations and upgrade procedures before production deployment.