Personal versus corporate AI accounts: telling them apart
A personal account is one signed in with a private email address; a corporate account is one in the company tenant. Browser extensions and identity records can tell them apart, tenant restrictions can enforce the split for some suites, and domain logs cannot.
Facts read on .
How do you tell a personal account from a work account?
Read the account at sign-in, not the domain. A browser extension sees which account a person is logged in to, an identity provider logs which tenant issued the sign-in, and an API connection to an enterprise AI service lists corporate seats. A proxy log only shows that the host was contacted.
Vendors document this signal. Akamai says its product can tell when a user reaches an AI tool with a personal rather than corporate account. Bay says its browser coverage detects corporate versus personal accounts, including personal Chrome profiles. Aurascape lists account type among its per-app attributes, and Harmonic says discovery covers personal accounts.
Sources: Akamai: AI usage control; Bay: browser platform; Aurascape: discover and monitor AI; Harmonic Security pricing.
What is tenant restriction?
Tenant restriction is a control that limits sign-ins on your network to a list of permitted identity tenants and blocks all others. In Microsoft's implementation, users on the network can reach only the tenants an admin lists, and other tenants are blocked even where the user is a guest.
Microsoft documents that a TLS-inspecting proxy inserts a header with the permitted tenant list into traffic to Entra ID, and that the feature covers apps that use Entra ID for single sign-on. It also supports blocking Microsoft consumer apps. It applies to Microsoft sign-ins, so it does not by itself separate personal and corporate accounts at other AI vendors.
Sources: Use tenant restrictions to manage access to SaaS apps.
Why does the difference matter for AI?
Corporate AI accounts come with contract terms on data use and retention, admin controls and logs. Personal accounts usually carry consumer terms, and inputs may be retained or used for training depending on settings. The same prompt carries different risk in each.
Per-tool terms vary, so record them. Nudge Security says it summarizes each AI vendor's training policy, opt-out options and retention, and Netskope says its risk scores include training on customer data.
Sources: Nudge Security: AI discovery solution; Netskope AI Command Center documentation; Netskope source (netskope-23).
What are the ways to enforce the split?
Four ways exist: tenant restriction for suites that support it, an enterprise license with SSO enforced, a browser control that warns or blocks personal logins, and a policy that routes users to an approved tool. Harmonic documents personal-account restriction, and Push Security documents warning with alternatives.
Combine a control with a clear approved alternative. Blocking a personal account without a corporate option moves use to unmanaged devices.
Sources: Harmonic Security: shadow AI detection; Push Security: shadow AI, how to discover, govern and secure AI apps.
What should the inventory record?
Record the account type per user per tool, and report the share of use on personal accounts by tool. A falling share after an enterprise license rollout is a clean metric for the board.
Keep the signal source with the number, since account detection from an extension and from an identity log can disagree.
What do users need to hear?
Users need a short rule and an easy alternative: use the company account for work, here is where to sign in, and here is whom to ask. A rule of this form can be delivered where the user is, at the moment a personal login is detected.
Document the rule where the user will see it. Push Security describes warning users with alternatives, and Nudge Security describes delivering the AI acceptable use policy through its browser extension, which puts the text next to the action.
Sources: Push Security: shadow AI, how to discover, govern and secure AI apps; Nudge Security: browser extension.
Sources
- Akamai: AI usage control (akamai.com), read
- Bay: browser platform (bay.io), read
- Aurascape: discover and monitor AI (aurascape.ai), read
- Harmonic Security pricing (harmonic.security), read
- Use tenant restrictions to manage access to SaaS apps (learn.microsoft.com), read
- Nudge Security: AI discovery solution (nudgesecurity.com), read
- Netskope AI Command Center documentation (docs.netskope.com), read
- Harmonic Security: shadow AI detection (harmonic.security), read
- Push Security: shadow AI, how to discover, govern and secure AI apps (pushsecurity.com), read
- Nudge Security: browser extension (nudgesecurity.com), read