Log in to your domain’s account at your domain host.
Verify ownership of a domain
- Adobe Enterprise & Teams: Administration guide
- Plan your deployment
- Basic concepts
- Deployment Guides
- Deploy Creative Cloud for education
- Set up your organization
- Identity types | Overview
- Set up identity | Overview
- Set up organization with Enterprise ID
- Setup Azure AD federation and sync
- Set up Google Federation and sync
- Set up organization with Microsoft ADFS
- Set up organization for District Portals and LMS
- Set up organization with other Identity providers
- SSO common questions and troubleshooting
- Manage your organization setup
- Manage products and entitlements
- Manage users
- Administrative roles
- User management techniques
- Change user's identity type
- Manage user groups
- Manage directory users
- Manage developers
- Migrate existing users to the Adobe Admin Console
- Migrate user management to the Adobe Admin Console
- Manage products and product profiles
- Manage products
- Manage product profiles for enterprise users
- Manage automatic assignment rules
- Review product requests
- Manage self-service policies
- Manage app integrations
- Manage product permissions in the Admin Console
- Enable/disable services for a product profile
- Single App | Creative Cloud for enterprise
- Optional services
- Manage Shared Device licenses
- Manage users
- Manage storage and assets
- Asset migration
- Reclaim assets from a user
- Student asset migration | EDU only
- Manage services
- Adobe Stock
- Custom fonts
- Adobe Asset Link
- Adobe Acrobat Sign
- Creative Cloud for enterprise - free membership
- Deploy apps and updates
- Create packages
- Customize packages
- Deploy Packages
- Manage updates
- Adobe Update Server Setup Tool (AUSST)
- Adobe Remote Update Manager (RUM)
- Create packages using Creative Cloud Packager (CC 2018 or earlier apps)
- About Creative Cloud Packager
- Creative Cloud Packager release notes
- Application packaging
- Create packages using Creative Cloud Packager
- Create named license packages
- Create packages with device licenses
- Create a license package
- Create packages with serial number licenses
- Packager automation
- Package non-Creative Cloud products
- Edit and save configurations
- Set locale at system level
- Manage your account
- Manage your Teams account
- Assign licenses to a Teams user
- Add products and licenses
- Automated expiration stages for ETLA contracts
- Switching contract types within an existing Adobe Admin Console
- Purchase Request compliance
- Value Incentive Plan (VIP) in China
- VIP Select help
- Reports & logs
- Get help
As a customer of Adobe Enterprise products and services, you need to claim a domain to set up enterprise user accounts. To prove the ownership of the domain, the DNS administrator needs to add a TXT record with the token generated in the Adobe Admin Console.
Add DNS record to your domain host's DNS settings
Find the page for updating your domain’s DNS record. This page may be called DNS Management, Name Server Management, or Advanced Settings.
Add the TXT record with the value adobe-idp-site-verification=<token>, where token is the number provided in the Admin Console.
For example, If your token is ”asdfadgalfjsadr3232324sdfesf” then the TXT record would be:
@ 3600 IN TXT "adobe-idp-site-verification=asdfadgalfjsadr3232324sdfesf"
To add the verification record to your domain host. Do the following:
- For the record type, select TXT.
- For the Name/Host/Alias field, enter @ or leave blank.
- In the Time to Live (TTL) field, enter 3600 or use default.
- In the Value/Answer/Destination field, paste the Record Value you copied from the Adobe Admin Console.
The field names for your domain host may vary.
Save the record.
If you see a warning, disregard it. Modifying or adding TXT records will not damage your website or DNS settings.Note:
The label for the TXT record must match the domain being claimed.
Once you've updated the TXT record, you'll need to return to the Adobe Admin Console and validate the domain.
Find the answer to some common questions here:
After you've updated any DNS records it may take anywhere between 24 to 72 hours to work properly. Domain hosts refer to this wait time as the "propogation time" it takes for changes to reflect across the internet.
If you're attempting to validate your domain in the Adobe Admin Console and it's not working, you can verify if the DNS TXT record has been updated and contains a value similar to: @ 3600 IN TXT "adobe-idp-site-verification=asdfadgalfjsadr3232324sdfesf"
You can use any DNS look up service to check the real-time status. For example, use enter your domain name in the G Suite Toolbox Dig to retrieve DNS records for your domain.
While the exact instructions to update the DNS Record will be provided by your domain host, you can use some publically available instructions. For example, you could check if instructions for your domain host are available on the Verify your domain help pages for G Suite apps. Once the TXT record has been updated and verified, you can return to the Adobe Admin Console to complete the set up.