Table of Contents

Transition to Altus Admin Consent

This page explains how customers move from Sensei (Legacy) enterprise app consent to the new Altus consent model.

Completing this transition early helps ensure a smooth move to the Altus application suite and ongoing access to Hub services.

Why this transition matters

During the transition period, Sensei and Altus enterprise apps can co-exist in the same tenant. This allows customers to migrate in a controlled way.

At the end of this calendar year, HubV1 will be switched off. Completing the new Altus admin consent before that date keeps your tenant ready for uninterrupted service on the current platform.

Transition to Altus Admin Consent

  • Enables a smoother move to HubV2 and connected Altus applications.
  • Supports a single, streamlined admin consent path for the Altus application suite.
  • Aligns your tenant with Altus app publisher verification.
  • Reduces last-minute risk as the HubV1 switch-off date approaches.

Key timeline

  • Now: Plan and schedule tenant admin consent for Altus.
  • Transition period: Legacy and new enterprise apps can co-exist while your teams validate access.
  • End of year: HubV1 is decommissioned, and Altus consent becomes the required path.
  • Post switch-off: Tenants with completed Altus consent continue using supported Hub services.
  1. Have an M365/Entra ID administrator perform the new Altus admin consent.
  2. Validate that the new enterprise applications are created in Entra ID.
  3. Confirm access to HubV2 and connected applications.
  4. Update internal runbooks and remove reliance on HubV1 before the end-of-year deadline.

Expected tenant state during transition

  • Legacy enterprise apps: Existing from prior Sensei consent, temporarily retained.
  • New enterprise apps: Created from Altus consent and used by current Altus services.

Validation checklist

  • New Altus consent is completed by a tenant administrator.
  • Users can access HubV2 successfully.
  • Dependent Altus applications authenticate with new enterprise apps.
  • Internal runbooks and support contacts are updated with the new consent path.

Frequently Asked Questions

What parts of Altus are affected?

Each part of Altus has a dedicated enterprise app, and each one is moving from Sensei to Altus.

Why is this change necessary?

This change streamlines installation through a single admin consent flow for the Altus suite and aligns with Altus app publisher verification.

Can we keep running while we transition?

Yes. During the transition period, legacy and new enterprise apps can co-exist so teams can migrate and validate in phases.

What should we verify right after consent?

Confirm that the new enterprise apps appear in Entra ID, users can sign in to HubV2, and connected Altus applications authenticate successfully.

Do end users need to do anything?

In most cases, no direct end-user action is needed. Tenant admins should complete consent and validation, then communicate any local rollout steps if required.

How long does this activity typically take?

The consent step is usually quick, but you should allow time for internal change planning, validation, and communications.

What if we complete consent well before the switch-off date?

That is recommended. Early completion gives your team more time to validate and reduces timeline pressure.

Will my application stop working?

Applications that depend on the new Altus enterprise app registration continue to work when consent is completed. If consent is not completed by switch-off, affected services cannot authenticate through the legacy path.

Do I need to transition to HubV2?

No manual transition is required. We will automatically migrate all instances from HubV1 to HubV2 using the same settings. After migration, instances are removed from HubV1. Please note that deployment history is not migrated.

Support and escalation

If assistance is needed with consent execution or tenant validation, contact your Altus partner or Altus support before the end-of-year cutoff.

Warning

Customers that do not complete new Altus admin consent before HubV1 switch-off may experience service interruption.

Edit this page