|
Changes to...
| Effective on |
Actions for Changes
|
Compliance Solution
|
|
Title Naming Convention
|
New workspaces
|
To apply to existing workspaces, use the 'Update details' Action on all requiring the change
|
A Title Mismatch - Align rule can be used to align to the Service Definition default to enforce a change and maintain the naming convention defined.
|
|
URL Naming
|
New workspaces
| To apply to existing workspaces, use the 'Change URL' Action on all requiring the change | A URL mismatch - Align rule can be used to align to the Service definition default or to regular expression to enforce a change and maintain the URL naming convention defined. |
| Additional Information on Request forms |
New workspaces
|
To apply to existing workspaces, use the 'Update details' Action on all requiring the change
|
n/a
|
|
Directory Visibility
|
New workspaces
| To apply to existing workspaces, use the 'Change Directory Visibility' Action on all requiring the change |
n/a
|
|
Additional Visibility
|
New & existing Workspaces
| Will be applied to all items related to the Service Definition |
n/a
|
|
Privacy Settings
|
New workspaces
|
To apply to existing workspaces, use the 'Change Privacy' action to make changes on workspaces.
|
Privacy Mismatch - Align rules can be used to align to the Service Definition default or specific values to enforce a change and maintain privacy settings. They can also be used to highlight if the privacy is changed in M365.
|
|
Guest Access & External Sharing
|
New workspaces
|
To apply to existing workspaces, use 'Change Guest Access' and 'Change External Sharing' Actions it will require the requestors to be able to change these setting
|
Guest Mismatch & External sharing mismatch - Align rules can be used to align to the Service Definition default or specific values to enforce a change and maintain the sharing options
|
|
Lease (recommend change to Lifecycle)
|
New workspaces
|
To apply to existing workspaces, use the 'Reapply Lease' Action on all requiring the change
|
n/a
|
|
Lifecycle
|
New Workspaces
|
If a Lease was already applied and an expiry date set, the lifecycle will be applied automatically.
If not, use 'Update details' action to set any form fields that control the lifecycle or 'Change the Lease' action to set the expiry date
|
n/a
|
|
Actions
|
New and existing workspaces
|
When an Action is enabled this will be available to all workspaces to the people granted permission.
|
n/a
|
|
Notifications
|
New and Existing workspaces
|
If Notifications are enabled or added, these will be respected for any workspaces created or existing. This includes updates to the notification templates
|
n/a
|
|
Approval
|
New workspaces
|
Approval can be applied to Actions managing changes but for creation will apply only to new requests.
|
n/a
|
|
Group Settings
| New workspaces |
Changes can be made to existing workspaces using Custom Actions, these can be used to trigger Azure runbooks or Power automate flows via a webhook.
|
n/a
|
|
Lists
| New Workspaces |
To apply to existing workspaces, use the 'Create' List' action on all requiring the change. There must be Lists setup with the 'Enabled for Create List Action'. This will be the template that can be chosen, multiple can be created.
|
n/a
|
|
Team Settings
|
New workspaces
|
Changes will need to be made in Microsoft Teams, go to Manage Team > Settings
|
n/a
|
|
Channels
|
New workspaces
| To apply to existing workspaces, use the 'Create Team Channel' Action on all requiring the change. One of the channels in the Service Definition will need to have the 'enable for the create channel action' set to Yes. This will be the template that can be chosen, multiple can be created. | n/a |
|
Planner
|
New workspaces
|
To apply to existing workspaces, use the 'Create Planner Plan' Action on all requiring the change. One of the Planner Plans in the Service Definition will need to have the 'enable for the create planner action' set to Yes. This will be the template that can be chosen, multiple can be created.
|
n/a
|
|
PnP Templates
|
New workspaces
|
Changes can be made to existing workspaces using Custom Actions, these can be used to trigger Azure runbooks or Power automate flows via a webhook.
|
n/a
|
|
Integration
|
New workspaces
| To apply to existing workspaces, use the 'Sync Directory' Action on all requiring the change | n/a |
|
Compliance
|
New and existing workspaces
|
When a Compliance Policy is linked this will be run on all workspaces linked to the Service Definition according to the schedule. For ad-hoc requests, the 'Check Compliance' Action can be run.
|
|