Altus Hub

Altus Hub is the self-service deployment and lifecycle management platform for Altus. It enables partners and customers to deploy Altus to Microsoft Power Platform environments, manage updates and release rings, and administer Altus subscriptions.

Use the Altus Hub portal to manage your Altus environments.

What you can do

Altus Hub provides a central place to:

• Deploy Altus to customer Power Platform environments.
• Manage solution updates and select a release ring.
• Configure automatic, approval-based, or manual updates.
• Manage administrators for Altus environments.
• View registered environments, deployment details, installed versions, and available updates.
• Load or remove demonstration data.

How Altus Hub works

Altus Hub manages deployment metadata, including registered Altus environments, installed solution versions, available releases, update status, and release-ring configuration. It does not host customer project, portfolio, or operational data.

The typical deployment lifecycle is:

1. Prepare the target environment, licensing, deployment access, and required Microsoft 365 services. See Technical Readiness.
2. Deploy the required Altus solutions, applications, reports, connections, and configuration to the selected Power Platform environment.
3. Authorise the environment for Hub-managed deployment and update operations.
4. Manage the environment's release ring and update policy.
5. Monitor deployment status and apply updates according to the selected policy.

For more information about the available release rings and update approaches, see Understanding Updates.

Security and administration

Altus Hub uses Microsoft Entra ID to authenticate users with their existing Microsoft 365 accounts. Altus does not store user passwords, and your organisation's Conditional Access and identity-governance controls continue to apply.

Deployment and update operations use the Deployment Service Principal (DSP), an application identity that operates only against authorised Altus environments. A customer administrator must grant the necessary consent before Hub can perform these operations. Customers remain in control of their consent and governance decisions.

For consent requirements and the enterprise applications involved, see Technical Readiness and Admin Consent Details.

Updates and release rings

Each environment can be assigned to the General Availability, First Release, or Canary release ring. You can configure the environment to receive updates automatically, require approval before an update, or use a manual update process.

Choose a release ring and update policy that aligns with your organisation's change-management practices. For customised deployments, use non-production environments to test updates before they reach production.

Transition from Sensei Hub

Altus Hub replaces the legacy Sensei Hub and is available at hub.altus.pro. The transition consolidates Altus application registrations, consent, and administration under the Altus brand.

During the transition, existing deployments are moved to Altus Hub using their current settings. Deployment history is not migrated. For the current timeline, required consent, and customer actions, see Transition to new Altus Admin Consent.

Legacy Sensei consents

During the transition period, the legacy Sensei and new Altus enterprise applications coexist. Customers must complete both the legacy Sensei and new Altus admin-consent processes while applications are being transitioned.

Do not remove the legacy Sensei consent during the transition unless advised by Altus, as it may still be required by legacy applications. From 1 February 2027, Altus Hub and the new Altus admin consent are required for continued Altus usage. Confirm that the new enterprise applications are present in Microsoft Entra ID and that Altus administrators can sign in to Altus Hub before making changes to the legacy consent.

Note

After the migration is complete, continue to manage Altus through the new Altus enterprise applications and consent. Only remove legacy Sensei consent when Altus confirms that it is no longer required.

Demonstration data

The Altus Demo Data Loader uploads or removes demonstration data in an Altus environment. Both consultants and clients can use this feature, provided they have access to the client's environment in Altus Hub.

For consultants

1. Sign in to the Altus Hub portal and open the Partner Admin section.
2. Select Altus for the client's environment.
3. Under Operations, select Edit for the environment where you want to load demonstration data.

For clients

1. Sign in to the Altus Hub portal and open the Altus section.
2. Under Operations, select Edit for the environment where you want to load demonstration data.

The Demo Data item is available from the Operations menu.

Select a date, then choose Load or Unload:

• Date picker: Sets the dates for the loaded data. Demonstration data is already three months old, so you do not need to backdate this value unless you want older data. It defaults to today's date, but you can select a past or future date.
• Load: Starts the demonstration data load process.
• Unload: Starts the demonstration data removal process. It removes data based on the current demonstration data for the selected release ring. If the demonstration data was upgraded and items were removed, manual removal may be required.

The Altus Demo Data Deployment Status screen shows the progress of the load or unload process.

Note

This screen does not refresh automatically. Refresh the page to see the latest progress value.

Note

The load and unload processes each take approximately 15 minutes.

Progress statuses:

• Running: The process has begun and is underway.
• Demo Data Loading/Unloading: Demonstration data is being loaded or removed.
• Success: The process has completed without major errors.
• demoDataLoadException: An error occurred during the load or unload process.
• demoDataLoadActivityException: An error occurred during the load or unload process.

When the process is complete, a Demo Data log file appears in the Deployed section.

• A green tick next to the Demo Data file indicates that the process completed successfully.
• A red lightning bolt next to the Demo Data file indicates that the process completed with errors.

Review the log file for details of the load or unload process. If the process does not complete successfully, no log file is available. Contact the Altus Product Development team to investigate.

Note

If the Load and Unload buttons are unavailable, a process is already running. Refresh the page to see its current status.