Skip to main content
Intune Commander stores connection details as profiles (tenant ID, client ID, cloud environment, auth method). Profiles are persisted locally in an encrypted file and never leave your machine.

​
Creating a New Profile

1

Launch the app

You’ll land on the login screen when not connected to a tenant.
2

Fill in tenant details

  • Tenant ID: Your Azure AD tenant GUID
  • Client ID: Your app registration client GUID
  • Cloud: Select from Commercial, GCC, GCC-High, or DoD
  • Auth Method: Choose Interactive (browser) or Client Secret
  • Client Secret (optional): Required only for Client Secret auth method
  • Profile Name (optional): Friendly name for the profile
3

Save the profile

Click Save Profile to persist it for future sessions. The profile is immediately added to the Saved Profiles dropdown.
The app validates that Tenant ID and Client ID are valid GUIDs before allowing you to save.

​
Using Saved Profiles

Once you’ve saved profiles, they appear in the Saved Profiles dropdown on the login screen.
1

Select a profile

Choose your profile from the dropdown. The form auto-fills with the saved credentials.
2

Connect

Click Login to authenticate. The last-used profile is automatically pre-selected on next launch.

​
Importing Profiles from JSON

You can import multiple profiles at once from a JSON file. This is useful for:
  • Distributing pre-configured profiles to your team
  • Migrating profiles between machines
  • Bulk-adding multiple tenant environments
1

Click Import Profiles

On the login screen, click the Import Profiles button.
2

Select JSON file

Choose a .json file containing one or more profile definitions.
3

Automatic merge

Profiles are merged into your existing profiles. Duplicates (same Tenant ID + Client ID) are automatically skipped.

​
Supported JSON Format

[
  {
    "name": "Contoso-Prod",
    "tenantId": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
    "clientId": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
    "cloud": "Commercial",
    "authMethod": "Interactive"
  },
  {
    "name": "Contoso-GCC",
    "tenantId": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
    "clientId": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
    "cloud": "GCC",
    "authMethod": "ClientSecret",
    "clientSecret": "your-secret-here"
  }
]
Valid cloud values: Commercial, GCC, GCCHigh, DoD Valid authMethod values: Interactive, ClientSecret, DeviceCode
A ready-to-use template is available in the source repository at .github/profile-template.json.

​
Managing Profiles

​
Editing a Profile

1

Select the profile

Choose it from the Saved Profiles dropdown.
2

Modify fields

Update any field (name, tenant ID, cloud, etc.).
3

Save changes

Click Save Profile again to persist your changes.

​
Deleting a Profile

1

Select the profile

Choose it from the Saved Profiles dropdown.
2

Delete

Click Delete Profile. You’ll be asked to confirm before the profile is removed.

​
Starting Fresh

Click New Profile to clear the form and create a new profile from scratch.

​
Profile Encryption

All profiles are encrypted at rest using Microsoft’s DataProtection API:
  • Storage location: %LocalAppData%\Intune.Commander\profiles.json
  • Encryption: File is prefixed with INTUNEMANAGER_ENC: marker and payload is encrypted
  • Key management: DataProtection keys are managed by the OS (Windows DPAPI, macOS Keychain)
  • Migration: Plaintext profiles from older versions are automatically migrated to encrypted format on first save
Profiles are machine-specific due to DPAPI encryption. If you need to share profiles across machines, export them to JSON before encryption or use the import feature on each machine.

​
Profile Switching

When connected to a tenant, you can quickly switch to another profile:
  1. Use the profile switcher dropdown in the app toolbar
  2. Select a different profile
  3. Confirm the switch when prompted
  4. The app disconnects from the current tenant and connects to the new one
Switching profiles re-authenticates and reloads data from the new tenant. Any unsaved work is lost.

​
Field Validation

FieldValidation
Tenant IDMust be a valid GUID
Client IDMust be a valid GUID
Client SecretRequired only when Auth Method = “ClientSecret”
Profile NameOptional; auto-generated from Tenant ID if empty

Build docs developers (and LLMs) love

Get started for freeTalk to us