Protecting a Microsoft 365 shared mailbox
Coro can protect Microsoft 365 shared mailboxes using the following two part process:
- Verify your shared mailbox is appropriately licensed by Microsoft 365
- Synchronize the shared mailbox with the Coro environment
Verify your shared mailbox is appropriately licensed by Microsoft 365
In order for Coro to effectively protect shared mailboxes, it is crucial that your account is appropriately licensed by Microsoft 365. This ensures that Coro can apply security measures to the mailbox and provide the necessary protection.
To ensure your shared mailbox is appropriately licensed by Microsoft 365:
-
Sign in to your M365 admin portal:
-
Select
Identity
(previously
Azure
):
-
Select
Users
>
All Users
:
-
Use
Search
to Locate the shared mailbox:
-
Select the username displayed next to
Identities
:
-
Select the
Properties
tab:
-
Locate the
Usage Location
field:
-
If
Usage Location
is blank, select
Settings
:
Coro displays the Settings page:
-
Select a location from the
Usage location
dropdown:
-
Select
Save
:
-
If
Usage Location
is blank, select
Settings
:
-
Select
Licenses
:
-
Select the Microsoft 365 license to assign to the shared mailbox:
-
Select the Microsoft 365 license options to assign to the shared mailbox:
-
Select
Save
:
- Refresh the page to confirm that the license is successfully attached to your shared mailbox.
Synchronize the shared mailbox with the Coro environment
After verifying your shared mailbox is appropriately licensed by Microsoft 365, synchronize the shared mailbox from the Coro Environment.
To synchronize the shared mailbox:
- Sign in to the Coro console .
-
From the sidebar, select
to access the Control Panel .
-
Select
Users
:
-
If you have already added protection to all users or if the shared mailbox is a member of a protected group, select
Sync
from the
Protected users
or
Protected groups
tab:
Coro syncs and protects the shared mailbox.
If the shared mailbox is not part of any protected groups, it must be added to protection individually.
For further information, see Adding users and user groups for protection.