How to make app trustable for OAuth / login as individual publisher?

Raiser 0 Reputation points
2026-11-18T04:53:21.3266667+00:00

Segue o texto revisado e corrigido em inglês, mantendo exatamente a sua ideia e o tom técnico:


Hi,

I am developing a dedicated desktop browser application for a web-based judicial/digital lawsuit management system. It focuses on workflow optimizations rather than relying on general-purpose browsers like Chrome, Vivaldi, Firefox, or Edge.

Since our official AI assistant is Microsoft 365 Copilot—which has deep integration in Microsoft Edge—I implemented an OAuth login flow in the app shell so users can authenticate with their Microsoft 365 Enterprise/Commercial accounts and use Copilot with tab-context reading capabilities. This avoids manually uploading case files to the cloud and helps enforce better LGPD (data protection) practices.

However, when I try to sign in, Microsoft Entra ID displays a message stating that the publisher is unknown/unverified and blocks the sign-in due to tenant consent policies.

I understand that an individual tenant administrator can manually grant admin consent, but my application is intended to be used across many different courts that run the same judicial system. Therefore, the OAuth sign-in needs to be trusted across multiple organizational tenants so any user can sign in and use the Copilot tab-context integration.

I searched the official documentation for options available to independent/individual developers (without a registered company/CNPJ) to obtain Publisher Verification or a trusted status in Microsoft Entra ID, but the documentation is not clear on whether any path exists.

Is there any supported way for an individual open-source/independent developer to become a verified publisher for multitenant OAuth apps in Microsoft Entra ID?

Thank you for your help.

Microsoft Security | Microsoft Entra | Microsoft Entra ID
0 comments No comments

1 answer

Sort by: Most helpful
  1. Vasileios Dionysopoulos 826 Reputation points
    2026-11-19T09:54:40.0766667+00:00

    Hi Raiser,

    Short answer: no, not as an individual. Publisher verification requires a Microsoft AI Cloud Partner Program account that has completed business verification, and that account must be the partner global account for the developer's organization. The app also has to be registered in a work or school tenant linked to that account, with a DNS-verified custom domain as its publisher domain (*.onmicrosoft.com isn't accepted). Without a legal entity behind it, there's no path to the blue badge.

    Even with the badge, verification wouldn't solve your case by itself. It only helps in tenants whose consent policy allows users to consent to apps from verified publishers, and only for low-risk permissions. Courts usually block user consent entirely, so you'd still hit admin consent.

    For your scenario, I'd set it up like this:

    1. Admin consent per court (works today, no verification needed)

    Give each court's IT a one-click admin consent link for your multitenant app:

    https://login.microsoftonline.com/{court-tenant-id}/adminconsent?client_id={your-app-client-id}
    

    A Cloud Application Administrator approves it once, and every user in that court can then sign in without the warning. Keep the requested permissions to the minimum (sign-in, plus only the delegated scopes you actually call). That makes the approval much easier for their security teams.

    2. Long term: let an institution be the publisher

    If the system is shared by many courts, the organization that owns or coordinates it (with a CNPJ and its own domain) can register the app in its tenant and complete publisher verification. The app then shows that institution as the verified publisher, which courts are also more likely to trust than an individual developer.

    Was this answer helpful?

    0 comments No comments

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.