Deployment Guide
3. Pre-Deployment Checklist
This section outlines the prerequisites that must be completed before deploying SmartOfficeNXT into a client or silo environment.
3.1 Accounts and Permissions Required
Microsoft 365 Administrator Roles
- The following administrative access may be required depending on the client’s governance model:
- Global Administrator / SharePoint Administrator
- Create or validate SharePoint site collections required for SmartOfficeNXT
- Upload and deploy the SmartOfficeNXT package file into the App Catalog
- Approve permissions requested by the application
SmartOfficeNXT Deployment Access
- The deployment team must have Owner permissions on the SharePoint site where SmartOfficeNXT will be deployed.
- This access is necessary to configure lists, libraries, and workflow components.
Service Accounts (If Required by Client IT Policy)
- Some clients may prefer dedicated service accounts for:
- API calls
- Power Automate connections
- SharePoint/Graph integrations
- These accounts should be restricted following least-privilege principles.
3.2 Certificates, API Keys, Licenses
Azure App Registration
If SmartOfficeNXT requires integration with Microsoft Graph or external services, the client must provide an Azure App Registration with:
| Parameter | Purpose |
| Tenant ID | Identifies the Microsoft Entra (Azure AD) tenant |
| Client ID | Identifies the registered application |
| Client Secret | Used for secure authentication |
| Redirect URI | URL for SmartOfficeNXT authentication callback |
| API Permissions | Example: Sites.Read.All, User.Read.All |
Microsoft 365 Licenses
- Users interacting with SmartOfficeNXT require appropriate licenses, typically including:
- SharePoint Online
- Power Automate (for workflow execution)
- Microsoft Teams (optional notifications)
- Outlook (email approvals/notifications)
3.3 Environment Preparation
SharePoint Site Collection
- The SharePoint site where SmartOfficeNXT will be deployed should be:
- Created
- Accessible
- Assigned with the necessary permissions for the deployment team
- This site will host the application, lists, libraries, and workflow components.
Lists and Libraries
-
SmartOfficeNXT requires a set of backend lists and libraries. These can be:
-
Automatically provisioned through the onboarding steps, or
-
Imported using a provided site template (if applicable)
All lists must have:
- Proper schema (fields, types, validations)
- Required permissions
- Versioning enabled (recommended)
Power Automate flows
SmartOfficeNXT uses Microsoft Power Automate to support its automated processes.
These flows handle platform-level automation tasks required for smooth operation and are deployed as part of the solution package.
During deployment, the required flows are imported, configured with the necessary connections, and enabled within the client’s Microsoft 365 environment.
Before deployment:
- Ensure the deploying user has permissions to import and enable flows
- Ensure required connections (SharePoint, Outlook, Teams, etc.) are available
- Flow deployment will be included as part of the installation steps.
App Catalog Availability
- SmartOfficeNXT requires one of the following to be available:
- Tenant App Catalog or Site Collection App Catalog
- This catalog is required to upload and deploy the “.sppkg” file.
Package Preparation
- The SmartOfficeNXT package should be pre-built and ready for upload.