Skip to content
English
Customer Portal
  • There are no suggestions because the search field is empty.

APIs and connectors: overview of API 2.0, app registrations, and connector changes

Mavim is introducing API 2.0 to support modern integrations and connectors such as the Power Platform connector and the SharePoint connector. API 1.0 remains available for now, so customers can transition gradually. Both existing and new app registrations can run side by side, allowing organizations to adopt the new architecture without disrupting current integrations.

This article explains:

  • The new app registrations required for API 2.0

  • Changes to the SharePoint connector

  • Updates to the Power Platform connector

  • What the April 2 deadline means

  • What will change after June 1

App registrations for API 2.0

The new release introduces four app registrations that support API 2.0 and related connectors.

1. Mavim Cloud – Identity Core Access

The Mavim Cloud – Identity Core Access app registration is required for all customers.

It acts as the central authentication component for accessing:

  • Mavim

  • Mavim integrations

  • API 2.0-based services 

Think of this as the main controller for authentication.

2. Mavim Cloud – Identity Web Application Access

The Mavim Cloud – Identity Web Application Access app registration supports access to iMprove, MPM (Process Mining) and MCC (Connectcenter).

3. Mavim Cloud – Identity Power Platform Access

The Mavim Cloud – Identity Power Platform Access app registration is required for customers using the Power Platform connector 2.0.

It must be installed together with the Mavim Cloud – Identity Web Application Access app registration.

4. Mavim Cloud – Identity API Access

The Mavim Cloud – Identity API Access app registration is intended for developers who build custom applications using the Mavim APIs.

This also requires the Mavim Cloud – Identity Web Application Access app registration.

App registration combinations

Use case Required app registration(s)
Prerequisite to access Mavim products (except Portal and Manager) Mavim Cloud – Identity Core Acces
All "customer facing" "web-based" frontend products (except Portal and Manager) Mavim Cloud – Identity Web Application Access
Power Platform connector 2.0 Mavim Cloud – Identity Core Acces + Mavim Cloud – Identity Power Platform Access
Custom API development Mavim Cloud – Identity Core Acces + Mavim Cloud – Identity API Access

SharePoint connector 2.0

Mavim is introducing SharePoint connector 2.0 due to Microsoft retiring Azure ACS authentication.

Reference:
Azure ACS retirement in Microsoft 365 (Microsoft Learn)

Current SharePoint integration

The existing integration has two components:

  1. Mavim Portal publishes term sets to SharePoint

  2. Mavim Portal accesses files stored in SharePoint

Changes in the new implementation

SharePoint connector 2.0 introduces the following updates:

  1. Term set publishing will no longer be required

  2. Mavim Portal connects to SharePoint using certificate authentication (same approach used in the current hotfix)

  3. SharePoint to Mavim data connections will be handled by a new SharePoint web part

  4. The new web part connects through Mavim APIs 2.0

  5. Customers must install the new app registrations 'Mavim Cloud – Identity Core Acces' + 'Mavim Cloud – Identity API Access' to use the new connector

If customers cannot install the new app registrations

Customers can continue using the existing SharePoint connector by:

  • Using certificate authentication (hotfix solution)

  • Continuing to publish the term set as currently configured

However, if Microsoft retires certificate-based authentication in the future, customers will need to move to the new connector and app registration model.

April 2 deadline

The April 2 deadline remains valid, but it is not blocking unless Microsoft disables the certificate authentication route.

Power Platform connector 2.0

The Power Platform connector 2.0 is currently in the Microsoft certification process.

  • Resubmission is planned for the week of March 9, 2026

  • The connector is currently under internal testing

Key characteristics

  • Works only with Mavim APIs 2.0

  • Customers must install the new app registrations 'Mavim Cloud – Identity Core Acces' + 'Mavim Cloud – Identity Power Platform Access'

  • Will be available through the Power Platform marketplace

  • Includes a license validation check


Existing Power Platform connector (v1.0)

The current Power Platform connector 1.0 will continue to work with existing app registrations.

Because of this:

  • Old and new app registrations can coexist

  • Customers can migrate gradually

Moving to Power Platform connector 2.0

To use the new connector:

  1. Install the new app registrations

  2. Use Power Platform connector 2.0

  3. Rebuild existing flows and apps using the new connector

April 2 deadline

The April 2 deadline still applies, but it does not block existing connector usage.

Access to Mavim and MCC

Access to Mavim via MCC will only be affected if customers use API 2.0-based components, such as:

  • Power Platform connector 2.0

  • SharePoint connector 2.0

  • Mavim APIs applications

In these scenarios, customers must install:

  • Mavim Cloud – Identity Core Acces app registration

  • The specific app registration for the connector or component

If customers do not use API 2.0 components, MCC will continue to function with existing app registrations.

April 2 deadline

Again, the deadline remains valid but not blocking.

Impact timeline

Component Impact on April 2 Impact after June 1
Mavim access via MCC No impact unless API 2.0 components are used. Moving to new app registrations is recommended. Customers must move to the new app registrations. Old registrations will be deprecated and unsupported.
SharePoint connector No impact unless Microsoft introduces additional authentication changes. If that happens, customers must move to the new connector and app registrations. Customers must move to the new app registrations because old registrations will be deprecated.
Power Platform connector No impact for customers using connector 1.0. To use connector 2.0 features, customers must install new app registrations and use the new connector. Customers must move to the new app registrations because old registrations will be deprecated.

Next steps

To prepare for the transition:

  1. Review whether your organization uses:

    • SharePoint connector

    • Power Platform connector

    • Custom API integrations

  2. Plan the installation of the new app registrations

  3. Evaluate whether you want to migrate to:

    • SharePoint connector 2.0

    • Power Platform connector 2.0

  4. Prepare for the mandatory migration before June 1, when older app registrations will no longer be supported.

© 2025 Mavim. All rights reserved.