Skip to main content

​
Automatic DNS

Automatic DNS lets TenantCore configure supported Microsoft 365 DNS records for domains already added to your TenantCore account. It is available on Plus, Complete, and the 14-day Plus trial.

​
Supported direct providers

Current direct-provider support includes:
  • Porkbun
  • Cloudflare
  • Namecheap

​
Before you begin

You need:
  • a domain already added to TenantCore
  • a supported provider connection for the same TenantCore account
  • access to the provider account
  • a plan that includes Automatic DNS

​
Start Automatic DNS

  1. Open the domain.
  2. Open the DNS/setup view.
  3. Choose Automatic DNS.
  4. Review the proposed setup.
  5. Start provisioning.
TenantCore creates a persistent provisioning workflow rather than trying to complete every external DNS and Microsoft step in one browser request.

​
What TenantCore does

The workflow can include:
  1. identify the connected provider
  2. build the Microsoft 365 DNS plan
  3. apply supported records
  4. wait for public DNS propagation
  5. verify the domain with Microsoft
  6. retrieve DKIM records when Microsoft exposes them
  7. publish DKIM records
  8. enable DKIM
  9. run final checks

​
Why the setup can take time

TenantCore controls the automation, but it does not control:
  • DNS propagation
  • Microsoft domain-verification timing
  • when Microsoft makes DKIM configuration available
You can leave the page while background reconciliation continues.

​
If action is required

If TenantCore encounters a condition that cannot be safely resolved automatically, the domain can show that operator action is required. For example:
  • provider access is unavailable
  • an existing DNS record conflicts with the required setup
  • the provider refuses a write
  • a Microsoft prerequisite is incomplete
Use the domain’s DNS details to see what remains.

​
Retry behavior

A failed provisioning job can be retried after the underlying issue is corrected. TenantCore keeps the provisioning run and job state so retries do not require rebuilding the domain from scratch.

​
API automation

On Complete, the same workflow can be started through the public API using a TenantCore-owned domain_id. The API does not expose raw Porkbun, Cloudflare, or Namecheap endpoints.