Share via

After Publishing Custom App for my org I got this error "This app is not available. Please check with your admin for more details" when I try to add that custom app

Customer Support 0 Reputation points
2025-10-23T14:24:51.42+00:00

Hello Microsoft Teams Support,

I am experiencing an issue with a custom Teams app published within our organization.

After successfully publishing the app for our organization and receiving admin approval, I attempted to add or open the app in Microsoft Teams. However, I am encountering the following error message:

"This app is not available. Please check with your admin for more details."

The app version is successfully published and approved and listed under Built for your org, but it still cannot be accessed or installed by users (including myself).

Could you please help investigate why the app remains unavailable even after approval and publication?

Thank you for your assistance.

Microsoft Teams | Microsoft Teams for business | Teams and channels | Other
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Celso Silva 0 Reputation points
    2026-05-28T02:01:10.0266667+00:00

    Most likely cause: App Permission Policies

    Even after publishing and approving, the app won't be accessible until it's explicitly allowed via policy.

    Steps to resolve:

    1. Teams Admin Center → Teams apps → Manage apps
      • Find your custom app and confirm its status shows "Allowed" (not "Blocked")
    2. Teams Admin Center → Teams apps → Permission policies
    • Check the policy assigned to your users
      • Ensure "Custom apps" is set to Allow all or the specific app is whitelisted
      • If using a custom policy, verify your users are actually assigned to it
      1. Teams Admin Center → Teams apps → Setup policies
        • If you want the app pinned/auto-installed, confirm the setup policy includes it and is assigned to users
        1. Org-wide app settings
          • Teams Admin Center → Teams apps → Manage apps → Org-wide app settings
            • Confirm "Allow interaction with custom apps" is toggled On
            1. Propagation delay
              • Policy changes can take up to 24 hours to propagate across the tenant — if you just approved it, wait and retry

    For GCC tenants specifically (relevant to your CMS environment), custom app policies can sometimes require an additional explicit allow at the org-wide level due to stricter defaults.

    The most common fix is #2 — the permission policy blocking custom apps even after the app itself is approved.

    Was this answer helpful?

    0 comments
  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    2 deleted comments

    Comments have been turned off. Learn more

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.