Share via

How to prevent users from logging into personal ChatGPT/Claude accounts on corporate devices using Microsoft Security Stack?

DAVAADEMBEREL PU 5 Reputation points
2026-03-02T07:13:48.0366667+00:00

Hi everyone,

I am looking for a robust way to enforce Corporate-only access to Generative AI platforms (specifically ChatGPT and Claude) across our organization.

The Goal: Users should be able to log in using their Corporate Entra ID (SSO), but they must be blocked from using personal accounts (Google, Apple, or personal email) while on corporate-managed devices or the corporate network.

The Challenge: Standard MDCA (Defender for Cloud Apps) Session Policies only trigger if the user initiates login via Entra ID. If they go directly to chatgpt.com and use "Continue with Google," they bypass our Conditional Access policies entirely.

I am looking for the best Microsoft-native approach to solve this. Which of the following is recommended, or is there another way?

Microsoft Global Secure Access (SSE): Can it perform "Tenant Restrictions" or HTTP Header Injection for non-Microsoft apps like OpenAI/Claude?

Microsoft Purview / Endpoint DLP: Is it possible to block the login page itself or restrict authentication to specific domains?

Microsoft Edge Management: Can we use "Site Permissions" or "Managed Preferences" to restrict the OAuth providers allowed on these sites?

Defender for Endpoint (MDE): Can "Custom Indicators" or "Web Content Filtering" be granular enough to distinguish between login types?

I want to avoid a "cat and mouse" game with URLs. What is the official Microsoft "Best Practice" for preventing "Personal AI Account" usage while allowing Corporate usage?

Thank you in advance for your guidance!

Microsoft Security | Microsoft Defender | Other
{count} vote

1 answer

Sort by: Most helpful
  1. JimmySalian-2011 45,231 Reputation points
    2026-03-03T09:59:43.7566667+00:00

    Hi,

    As this is a wide topic for discussion, I would suggest you start with Defender for Cloud as this can allow you to block custom domain names and IPs based on the requirement. This is the article you can review and see if it helps - https://learn.microsoft.com/en-us/defender-endpoint/indicator-ip-domain

    Microsoft Purview will allow you to implement DLP and Label policy to control leakage of the data.

    So you can have multiple solutions provide coverage.

    Hope this helps.

    JS

    ==

    Please accept as answer and do a Thumbs-up to upvote this response if you are satisfied with the community help. Your upvote will be beneficial for the community users facing similar issues.


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.