1 item or a whole list
Select an item, or tick several. A change applies to the ticked items, or to the 1 you selected.
Controlled changes
See Each Change Before You Run It
A window shows what a change does, the items it applies to and the tenant it goes to. Run makes it, and the tenant's change log records it.
What you get
The tenant named
The change's window shows what it does, the items it applies to, any settings it needs and the tenant it goes to.
No run by accident
For a change that blocks or removes something, such as Block sign-in or Wipe a device, Enter doesn't run it. You select Run.
A change log
Each change goes in the tenant's change log, with the command sent and the values before and after.
How it works
Select, check, then run
Select the items
1 item, or tick several.
Choose the change
On the toolbar, under More or with a right-click.
Check it, then Run
The change log records it, and the page reads its list again.
Changes where you work
Each page has the changes for what it lists, from Microsoft 365 to Azure.
- The changes you make most often are buttons on the toolbar, such as Block sign-in for users. The rest are under More, grouped by service, with the ones you used last first, and a right-click offers every change.
- A licence is chosen from the tenant's products, with their free seats. Search finds people and groups, and lists only what the change can act on.
- Intune policies and Autopilot profiles are assigned to a group, all users or all devices, and keep their other assignments.
- A tenant-wide setting shows its current value and the exact command for the new one. A change that weakens security, such as turning off the unified audit log, shows a warning first.
- To make a change again later, or over the rows of a CSV file, create a workflow from it.
A change log for each tenant
Every change that's sent is recorded when it's sent: from a page, a workflow, a blueprint or a tenant-wide setting.
| Column | Shows |
|---|---|
| Time | When the change was made |
| Change | The change, such as Block sign-in. A change made by a workflow or a blueprint names it too |
| Target | What was changed, such as a user or a mailbox |
| Status | Done, No change, Failed or Stopped |
| Detail | What happened, or why it failed |
| Settings | The values entered for the change |
| Signed in as | The app, for certificate sign-in, or the administrator who signed in |
| Windows account and Computer | Who made the change, and on which computer |
| Command | The command that was sent |
| Before and After | The values the change read before it, and after it, where it reads them |
- Each tenant's change log is a CSV file in its folder on your computer, ready to open in Excel.
- A change stopped part way says how much was made, such as 2 of 5 commands.
- Altivane never sends a change again when it isn't sure whether the first try worked. The change shows as failed, and the record that it was sent stays.
- Refreshing a page, running reports and test runs of workflows change nothing, so they aren't recorded.