Decommissioning or updating the deployment account credentials

Altus is designed to function without external interactive access to your environment. This is an important point for those customers who have regulatory requirements with regard to third party data access.

During deployment your consultant will utilise their Deployment Account to setup and customise the system. This may lead to the Deployment Account becoming the owner of certain key pieces of the infrastructure:

• Microsoft Power BI Report Dataset Scheduled Refresh
• Microsoft Power Automate Cloud Flow Data Connections
• Microsoft Power Apps Dataflows (Optional Project/Task Synchronization from External Execution Tools)

While we recommend keeping this account active to allow the consultant to provide ongoing assistance with enhancements and customisations to the client system or provide troubleshooting support, some clients will prefer to either:

1. Decommission this account post deployment.
2. Change the password to this account, while still keeping it active so as to keep running the services above under these credentials.

Before completing either of the above options, please review the above items to ensure that the ownership is transitioned to another identity (ideally an accountable user, who can view and respond to any failures in the Microsoft services).

To provide the best possible service and ongoing support to our clients, we recommend that engagement lead maintains their own set of credentials to the Power Apps environment to which Altus has been deployed (and potentially other services depending on the requirements).

To update the credentials used for Microsoft Power BI scheduled refresh

1. Log into Power BI using the account that you would like to use to take over the scheduled refresh service. This account must be a workspace administrator.
2. For each of the Altus Report Datasets, access the Scheduled Refresh page, and click Take over near the top of the page.
   
3. Confirm that you are taking over the dataset settings by clicking Take over again on the dialog that appears.
   
4. Under the setting for Data source credentials click Edit credentials to update the credentials used for the dataset. The new credentials must have READ access to the Dataverse tables for the Altus environment.
5. Lastly on the Configure DatasetName dialog, set the authentication method to OAuth and privacy level to Organizational and then click Sign in and sign in using the standard Microsoft Authentication dialog.
   

To update the credentials used for Microsoft Power Automate Cloud Flow Data Connections

1. Sign into the Power Apps Maker Portal using the account that you would like to take over the data connections.
2. On the quick launch menu, click Solutions.
3. Click the display name for the solution Atsumeru.
   
4. Using the content filter in the upper right of the page, select Cloud flow.
   
5. Click the display for the Cloud Flow Proposal Approval Atsumeru.
   
6. Once the cloud flow opens in Power Automate, in the Connection References box, click Edit.
   
7. Remove each of the connection references by clicking the X symbol. Go back to the cloud flow details page.
   
8. Click Edit to edit the cloud flow.
9. On the Connections page that is presented, click the + symbol next to each connection to update the credentials used for each. Click Save. Note: the new credentials used will require a license for each of the services associated to the connection reference (eg Microsoft 365 Outlook requires an Exchange license, included with E1, E3, E5 licenses).
10. Test the Flow.

To update the credentials used for Microsoft Power Apps Dataflows

Note

Updating credentials here may only be necessary if the password or credentials are updated for the account that has been used to connect to (query for) the external data being pulled into the Altus Dataverse.

1. Sign into the Power Apps Maker Portal using the account that you would like to take over the dataflows.
2. On the quick launch menu, under Dataverse click Dataflows.
3. Select All Dataflows and search for the owner of the dataflows to be replaced (in our example, we are taking over the dataflows owned by Tina Hamilton).
4. Click Change Owner for each dataflow that requires editing of the data connection credentials.
5. Enter the new user in the New owner input box, then click Change Owner at the bottom of the pane.
6. Once the owner has been changed for the dataflows required, assuming you are logged in as the new owner user, click My Dataflows.
7. For each dataflow that has had it's owner changed that requires the credentials to be updated, click the ellipsis, then click Edit.
8. Once the Power Query editor dialog opens, it will be likely that the connection will need to be configured. Click Configure connection.
9. On the Enter credentials dialog, first ensure that privacy level is set to Organizational, then set the authentication kind to Organizational Account and click Sign In then sign in using the standard Microsoft Authentication dialog. Note: you will not be able to use a browser that is in private or incognito mode for this step. Once authenticated, click Connect.
10. On the Edit queries step in the Power Query editor, if no modifications to the query are desired, click Next at the bottom right of the dialog.
11. On the Map tables step in the Power Query editor, confirm mappings and click Next.
12. On the Refresh settings step in the Power Query editor, update refresh settings if desired (We recommend automatic refresh every 1 days) and finalize by clicking Create.
13. Test the changes by ensuring that the dataflow refreshes without error (manual refreshes can be initiated at any time by clicking the ellipsis and clicking Refresh).

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.