Create SpinOne policies to automate onboarding, offboarding and add-ons management for your organization!
Remember that for each and every Security Policy, you can specify Scopes and Exceptions, outlining what users, Security Groups the policy should and should not apply to.
Policy 1 - Onboarding Entities
With new employees being hired and new Shared Folders being created everyday, it is imperative for organizations to ensure that their mission critical data is being protected. Through the Onboarding Entities security policy, administrators can now automate activation of entities.
The conditions of the Onboarding policy can detect:
-
Active Users- enabling this condition will allow the policy to detect active users
- New users - only new users who have been added to Office 365 after the policy has been enabled
- All users - all existing and all new users
-
Sharepoints - enabling this condition will allow the policy to detect active Sharepoints
- New Sharepoints - only new Sharepoints that have been created after the policy has been enabled
- All Sharepoints - all existing and all new Sharepoints
The policy can perform the following actions:
- Activate - activate all entities detected in the Conditions section. If a user is being activated, a license will be utilized
- Activate Autobackup - enables autobackup based on the configurations specified in the Autobackup section for Users and Sharepoints respectively
- Set storage location - specify where the entity's data will be stored. Admins can choose the default storage location for their organization, or specify a different area
- Auto-purchase - if there are no available licenses for activating a user, the policy will auto-purchase licenses utilizing the payment method on file
- Send notification - the policy will send a notification to the administrator notifying of what actions were taken place
Policy 2 - Offboarding Entities
Similar to automating entity onboarding, it is also necessary to streamline archiving, suspending backups and removal of entities that are no longer required.
The conditions of the Offboarding policy can detect:
- Suspended Entities - Users that have been suspended in Office 365 but have an active license assigned on SpinOne
- Deleted Entities - Users and Sharepoints that no longer exist in Office 365 but are protected on SpinOne
The policy can perform the following actions:
-
Change status- allows converting an activated entity to a different status
- Archive - replaces a main subscription license with an archive license for users
- Deactivate - deactivates the User or Sharepoint from SpinOne (NOTE: Deactivated entity data will be automatically deleted in 30 days. In case an entity has been accidentally deactivated, there is a 30 day grace period to reactivate)
- Suspend Backups - turns off autobackups for detected entities. This is useful for maintaining snapshot history
- Auto-purchase archive licenses - if there are no available archive licenses for archiving a user, the policy will auto-purchase licenses utilizing the payment method on file
- Send notification - the policy will send a notification to the administrator notifying of what actions were taken place
Policy 3 - Add-Ons Management
The Add-Ons management policy will allow administrators to manage:
- Storage Add-Ons - applicable to the SpinOne, SpinSecurity and SpinBackup subscription plans
- Apps Add-Ons - applicable to the SpinApps subscription plan only (NOTE: This subscription plan is currently under development for Office 365)
The conditions of the Add-Ons Management policy can detect:
- Unavailable Apps - when the number of applications detected is more than the limit on the subscription plan
- Storage Exceeded - activated when the allocated storage limit has been exceeded
The policy can perform the following actions:
- Auto-Purchase - the policy will auto-purchase the necessary add-ons to ensure complete protection utilizing the payment method on file