Deployment account
To enable the deployment engineer to perform the interactive activities necessary to deploy Altus to your environment, we require at least temporary access via a deployment account.
Requirements for the deployment account include:
- Must be accessible externally (from the internet)
- Must not be a guest account, as guest accounts cannot be used with all the features of Power Apps at this time. i.e. the account must be created in the same Azure Active Directory as the target M365 tenant.
- Licensed as per an end-user (see license section above). Power Apps Per User license is recommended for this account to make use of the Power Automate Flows that are included with Altus for notifications and approvals.
- Dynamics permissions: The deployment account will require System Administrator permission within the target Power Platform environment for deployment and customization activities.
- Teams Administrator: To allow us to deploy the Teams application and configuration policy for your users we require access to the Teams admin portal. To do this grant the deployment account access in the Office Admin Centre. This is a once-off activity that could also be completed by the customer IT governance team if desired.
Decommissioning the deployment account
While it is possible to decommission the Deployment Account post-deployment of Altus, there are some considerations to note as detailed in Reference here: Decommission or Update the Deployment Account
Warning
To prevent system downtime, please work with your engagement lead before either disabling the Deployment Account or changing the password for the Deployment Account.