Tenant Manager provides a clear view of the deployment lifecycle by assigning statuses to each deployment action. These statuses reflect the exact state of a deployment, allowing users to quickly understand progress, spot issues, and take appropriate action. Knowing what each status means is essential to managing your deployments effectively and ensuring the integrity of your tenant configurations.
Assette has made key improvements to the deployment process, including ensuring complete deployments and eliminating partial or ambiguous deployment states. The following sections explain each deployment status in full detail.
Deployed #
The Deployed status indicates that the deployment has been successfully completed to the target tenant without any issues. All configurations, data, and dependencies were transferred correctly, and the system has validated the outcome as complete. Once a deployment reaches this state, no further action is necessary unless additional changes need to be deployed later.
Unauthorized #
The Unauthorized status occurs when the user who initiated the deployment does not have the correct permissions in either the source tenant, the target tenant, or both. Tenant Manager verifies user permissions at the beginning of the deployment process. If the appropriate access rights are missing, the deployment is immediately halted and marked Unauthorized. Users encountering this status should review their role assignments in Assette Admin Center and ensure they have the necessary permissions in both tenants before retrying.
Pending Approval #
The Pending Approval status shows that the deployment requires formal approval from designated approvers within the Workbox before proceeding. Assette uses a governance model that allows deployments to be reviewed for compliance, completeness, and accuracy before finalization. Deployments remain in the Pending Approval status until an approver explicitly approves or rejects the request in Workbox. No changes occur in the target tenant until approval is granted.
Partially Deployed (Deprecated) #
The Partially Deployed status has been deprecated following an update on April 25, 2025. Previously, it indicated that some, but not all, elements of the deployment had completed successfully. This partial state created potential inconsistencies across tenants and made troubleshooting difficult.
With the April 25 update, Tenant Manager now enforces complete deployments only. Deployments must either fully succeed or fully fail; no middle ground is permitted. If a deployment cannot complete fully, it will now receive a Failed status instead. This change ensures operational consistency and removes the risk of semi-configured tenants.
Rejected #
The Rejected status means that the deployment was reviewed and explicitly rejected by one or more approvers in the Workbox. A rejection stops the deployment process completely, and no configurations are applied to the target tenant. Users should check the rejection comments left by the approvers to understand the reason for rejection and make any necessary corrections before reattempting deployment.
Initiated #
The Initiated status indicates that the deployment process has started but has not yet completed. During this stage, Tenant Manager is preparing resources, validating dependencies, and setting up necessary communication between the source and target tenants. Deployments typically move quickly from Initiated to another status (such as Deployed, Pending Approval, or Failed). If a deployment remains stuck in the Initiated status for an unusual amount of time, it may indicate a backend processing issue that should be investigated.
Failed #
The Failed status means that the deployment did not succeed and no changes were made to the target tenant. The reason for failure is stated and may include dependency errors, permission issues, data conversion problems, or environmental factors.
The following messages are displayed along with a “Failed” status:
- The operation has timed-out
- This occurs when the requested API has timed out. The default timeout is 150 seconds but may vary from tenant to tenant depending on configurations.
- Access to the path is denied
- This error occurs when the user has requested a resource to which they do not have access to API/Function app
- Deployment has failed due to error
- Deployment has failed due to an unidentified error
When a deployment fails, users are encouraged to review the error details provided, correct any issues, and then reattempt the deployment when ready. For further troubleshooting, contact clientservice@assette.com.