What is Deletion
When a Group Team, Site, Planner or community is no longer required it can be deleted in M365. Owners of the workspaces and Admins can process the deletion in Microsoft.
Once deleted it can be restore for up to 30 days from the Admin Centres of the relevant type.
Deletion in ProvisionPoint
Within our app we have actions and expiry actions for any workspaces that have a lifecycle. These can be used to process changes to workspaces once they have been created.
There are two deletion actions:
- Delete the Team, Site, Group, Planner, Community - This will send a request to Microsoft to delete the defined workspace. Once completed the type icon will show a deleted sign and the info will highlight this has been deleted. This will also limit the Actions available to 'Delete from the Directory' only.
- Delete from the Directory - This will delete the workspace from ProvisionPoint's Directory and any Site Directory Lists (if you have set the list to only flag deletion it will remain on the list)
What is a Deletion Mismatch?
If a workspaces has been deleted natively in M365, the instance in ProvisionPoint will not be updated automatically.
Use the compliance policy to update our app and each instance with the correct status. You can then use the filters in the directory to decide whether or not the workspaces should be deleted from the Directory.
Users will no longer be able to run actions that would fail and other compliance checks will no longer be run.
Define the mismatch value to look for and let the scheduled policy show you the results or make a change using the rules.
You can also ensure any changes made in O365 are applied to ProvisionPoint instances or vice versa.
Available rules:
| Rule name | Description |
| URL Mismatch - Report | Report only on the mismatch that is configured |
| URL Mismatch - Notify | Send an email to configured people about the non-compliance, this email will include content define in the rule. Additional configuration will be needed, read the Configure Notifications for Notify Rules article |
| URL Mismatch - Align | Align to M365, ProvisionPoint instance, a defined value |
We always recommend starting with a Report rule to ensure the policy brings back the results you expect before applying the action rules (Align)
Mismatch Types
The mismatch you choose will set what is going to be flagged as non-compliant.
| Mismatch Type | Description |
| Instances | The M365 workspace does not match the service instance shown in ProvisionPoint Workspaces Directory info |
|
Transform Tag
|
The M365 workspace or service instance do not match a transform tag value. A transform tag would be defined in a lookup or as a request variable in ProvisionPoint Workspaces. This value would be used to set the Privacy setting at provisioning.
Add the name of the request variable or lookup to the Mismatch value
|
| Defined values | The M365 workspace or service instance do not match any of the selected values set to Yes |
Align Types
If non-compliance is found the align type will set what changes will be applied.
| Align Type | Description |
| O365 workspace | Will set service instance to match the M365 setting |
| Service Instance | Will set the M365 workspace to match the service instance setting shown in Info |
| Defined values | Will set the M365 workspace and service instance to match the Align value |
| Transform Tag | Will set the M365 and service instance to match the value set by the transform tag set in Align value. This will be the name of the request variable or lookup. |
Check the Results:
Once a Compliance policy is run you can check the results in the Job Queue and in the Timeline if it is non-compliant.
Read the articles in the Job Queue section: