Microsoft 365 Message Center Archive

MC1240748 - Retiring the Impala connector

Message ID

MC1240748

View in Message Center

Service

Microsoft Power Automate in Microsoft 365

Published

Feb 28, 2026

Tag

Major change
User impact
Admin impact
Retirement

Act by

Mar 31, 2026

Summary

The Impala connector will be retired and removed from Copilot Studio, Logic Apps, Power Apps, and Power Automate between April 1-14, 2026. Existing connections will stop working, and new ones won't be allowed. Users should migrate to alternative connectors and update related documentation to avoid disruption.

More information

Introduction

We’re retiring the Impala connector across Copilot Studio, Logic Apps, Power Apps, and Power Automate. This change aligns with our efforts to streamline our connector catalog, reduce maintenance of legacy components, and focus on modern, widely adopted data connectivity options. After this retirement, the Impala connector will no longer be supported.

When this will happen

  • Retirement begins: April 1, 2026
  • Retirement completed: April 14, 2026

How this affects your organization

Who is affected

Organizations using the Impala connector in any of the following services:

  • Copilot Studio (Premium)
  • Logic Apps (Standard)
  • Power Apps (Premium)
  • Power Automate (Premium)

What will happen

  • The Impala connector will be retired and removed from Copilot Studio, Logic Apps, Power Apps, and Power Automate.
  • Existing connections using the Impala connector will stop functioning after the retirement window.
  • New connections using the Impala connector will no longer be allowed.
  • The connector and its actions—including Get row, Get rows, and Get tables—will no longer be accessible.

What you can do to prepare

To reduce service disruption:

  • Review your apps, flows, and Logic Apps that currently use the Impala connector.
  • Migrate any dependencies to supported alternative connectivity solutions (for example, connector options that support your organization’s Hadoop‑based environments).
  • Notify users and solution owners who rely on this connector.
  • Update internal documentation, runbooks, and helpdesk scripts to remove references to the Impala connector.
  • Learn more about the connector’s current capabilities and behavior through our documentation: Apache Impala | Connector reference | Connectors | Microsoft Learn

If your apps or flows require ongoing connectivity to Impala endpoints, consult your data platform owners to determine your long‑term connectivity strategy.

Compliance considerations

No compliance considerations identified. Review as appropriate for your organization.