Tenants

On this page, you can manage the tenants that you use with IntuneCD.

You can select one tenant to be the "baseline" tenant, which serves as the standard for other tenants to follow. This baseline tenant is considered the golden standard, and other tenants should use it as a reference point for their configurations.

Multiple instances can be created of one tenant, if you create example.onmicrosoft.com and set it as the baseline tenant, new instances with the same name example.onmicrosoft.com can use the baseline PAT (Personal Access token) so you do not have to configure it multiple times. Multiple instances can be beneficial if you want to backup and create multiple branches based on prefixes.

Add new

To add a new tenant, just click NEW TENANT. The following information is needed to add a new tenant,

• Display Name
• Tenant Domain (example.onmicrosoft.com)
• Git Repo URL (github.com/exampleuser/intunecd
  • If you do not want to use the baseline Git repo as the source, you can configure a separate repo here. If no repo is configured, the tenant will use the baseline repo.
• PAT (Personal Access token, if repo is configured)
• Update args
• Backup args (applicable only to tenants with a Git repo configured)
  • If the --prefix argument is provided here and the checkbox for Create new branch is checked, the name of the branch will be the same as the configured prefix
• Create new branch
  • If checked will push changes to a new branch instead of main with the name intunecd-backup-{date}

If no git repo is added to the tenant, the baseline repo will be used for updating.

Once clicking Save, you'll be redirected to authenticate with an account in the tenant you're adding and to accept the requested permissions.

Edit

Click the edit button and change the values you wish to change. Note that Tenant PAT should be left blank if you do not what to update the token.

When editing, new options shows up for a tenant, mainly the option to choose which branch a given tenant should use from the Git repo when running updates. If you for example backup configurations based on a prefix, a tenant can use that branch for updates. This can be useful if you want to target specific configurations to specific tenants. For the baseline tenant you can also choose to generate documentation that will be displayed in the /documentation page.