Adobe Commerce solution for personal Adobe account sign-up blocked by company email domain
If a user cannot create an Adobe account with a company email address, the organization’s domain is usually managed in Adobe Admin Console for enterprise or federated authentication. In that case, the user must be provisioned by an administrator and should sign in through the organization’s company or federated login flow, or use a personal email address for a separate standalone account.
Description description
Environment
- Adobe identity and sign-in flows
- Adobe Admin Console
- Federated authentication environments
- Adobe Commerce scenarios where users are trying to access Adobe-linked services
Issue/Symptoms
A user cannot create a new Adobe account with a company-managed email address from the public sign-up flow.
The user may see an error similar to:
You cannot use this email address to create an account. Please use a personal email address to create a new account.
Steps to reproduce
- Go to an Adobe account creation or sign-in page.
- Enter a company-managed email address.
- Attempt to create a new Adobe account using that email address.
- The sign-up flow is blocked, and an error message is displayed.
Cause
This behavior is expected when the email domain is claimed or managed by an organization in Adobe Admin Console. In these cases, the organization controls how identities are created and authenticated for that domain.
If the organization uses Enterprise ID or Federated ID, users are not expected to self-create a standalone public Adobe account with that work email through the normal public sign-up flow. Instead, the account must be provisioned by the organization, and sign-in may be routed through the organization’s single sign-on (SSO) process.
Resolution resolution
Use the path that matches the user’s goal:
Option 1: The user needs access through their company or organization
- Contact the organization’s Adobe System Administrator or internal IT team.
- Ask the administrator to provision the user in Adobe Admin Console or the connected identity provider.
- After provisioning is complete, sign in using the organization’s company or Federated login flow.
Option 2: The user needs a personal standalone Adobe account
If the user needs an account that is not managed by the organization, they must use a personal email address that is not claimed or controlled by the company’s Adobe identity setup.
Additional information
- This issue is generally not version-specific.
- The behavior is tied to identity configuration, not to a product defect.
- In federated environments, authentication is commonly handled through the organization’s SSO flow.