---
title: "App Fails To Deploy to Teams Catalog Due to Policies"
slug: "app-fails-to-deploy-to-teams-catalog-due-to-policies"
updated: 2025-09-29T04:24:53Z
published: 2025-09-29T04:24:53Z
canonical: "kb.connecttoteams.com/app-fails-to-deploy-to-teams-catalog-due-to-policies"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.connecttoteams.com/llms.txt
> Use this file to discover all available pages before exploring further.

# App Fails To Deploy to Teams Catalog Due to Policies

## Issue : **App Fails To Deploy to Teams Catalog Due to Microsoft Migration**

## Cause

An issue related to Microsoft’s migration to use App Centric Management causes an error when deploying apps to the Teams catalog. This issue results in an error like the one in the image below.

![](https://cdn.us.document360.io/312e5ae5-e3c1-465d-8e37-f253a7ba8eee/Images/Documentation/image(985).png)

## Solution

While waiting for Microsoft’s permanent fix, the following workaround can be done for app deployment:

1. When an app is deployed:
  - If the app is available in the catalog, it will be deployed immediately.
  - If the app is not available in the catalog, the status is set to Pending Catalog Verification. In addition, the spinner icon displays CATALOG VERIFICATION IN PROGRESS when hovered over.
2. Enterprise Admins can log in and click Verify [service name] App under the Action Required column. They need to click it periodically until it completes and disappears. When doing this, please ensure that they are using the Chrome browser.
3. When the app is available in the catalog, it completes the verification and is deployed as it used to.

![](https://cdn.elev.io/file/uploads/9NQm9mTU3cx1bAj3cgTNBoVxBykXKVSMw4riGN1mhA0/aBgDIyBQn4HyEVANWwLAfg9XrDWgfFhS4MtzxDyHWZw/1719415792739-dJA.jpeg)

> [!NOTE]
> NOTE
> 
> This workaround flow deploys the app within 48 hours instead of not being deployed at all.