Specifying who to protect [Microsoft 365 - API]

Modified on Sat, 7 Sep at 4:00 PM

 

  1. Specifying who to protect [Microsoft 365 - API]

 [This is also known as the plan.]

  1.  Protect the organization's entire Microsoft 365 account: Protects all email addresses in all the domains that are included in your organization's Microsoft 365 account. 

Note: Domains and email addresses that are added in the future to the organization's Microsoft 365 account will be protected.

  1. Protect the following entities only: Allows you to specify which domains, groups, and users [email addresses] to protect. 

 

 

 

Note: 

  • After onboarding a Microsoft 365 - API integration, you can't change the set of assets that are protected by Perception Point X-Ray. Changing the set of assets includes:
    • deleting any of the specified domains, groups, or users
    • specifying additional domains, groups, or users

Suggested workaround: To change the set of assets that are protected, first off-board the API integration, and then on-board it again, with the required protection configuration.

  • You can specify a maximum of 300 assets [domains, groups, and users] to protect.
  • Specific domains: Protects only the domains that you specify. All users inside the specified domains will be protected.

Note: Email addresses that are added [in Microsoft 365] in the future to any of the specified domains will also be protected.

  • Specific groups and users: Protects only the groups and users that you specify.

Note: 

  • Groups can be any of the following group types: Microsoft 365; Distribution; Mail-emabled security
  • Email addresses that you specify must be included in your Microsoft 365 account.
  • Email addresses that are added in the future [in Microsoft 365] to any of the specified groups will also be protected.
  • Specific domains, groups and users: Protects all the domains, groups, and users that you specify.

Note: 

  • Groups can be any of the following group types: Microsoft 365; Distribution; Mail-emabled security
  • Email addresses that you specify must be included in your Microsoft 365 account.
  • Email addresses that are added in the future [in Microsoft 365] to any of the specified groups will also be protected.

 

Note about future changes: 

  • Domains that are added to your Microsoft 365 account in the future will not be protected.
  • Email addresses that are added in the future [in Microsoft 365] to any of the specified domains or groups will also be protected.
  • Email addresses that are added to your Microsoft 365 account [outside of the specified domains and groups] in the future will not be protected.
  1. [This step may not appear] Select to where spam emails will be moved - to the user's Inbox or the Junk folder - if spam emails are not configured to be quarantined. 
    • Inbox: The email is sent to the user's Inbox. This setting is typically used for PoC installations - not for production installations.
    • Junk: The email is sent to the user's Junk folder. This setting is typically used in production installations - not in PoC installations. 

This setting can be changed after on-boarding. 

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article