Category | Microsoft Docs article | Related commit history on GitHub | Change details |
---|---|---|---|
admin | Email Collaboration | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/admin/email/email-collaboration.md | - Title: "Email collaboration"-- NOCSH-------- highpri -- M365-subscription-management -- Adm_O365--- VSBFY23-- AdminSurgePortfolio-- BCS160-- MET150-- MOE150-- MOW150-- OWE150-- OWP150-- SPO160-- BSA160-- SPB160 -description: "Learn about the various types of groups and how to use them with the various collaboration features of Microsoft 365." ---# Email collaboration in Microsoft 365 --Microsoft 365 encourages collaboration through Groups in Outlook, distribution lists (also called distribution groups), shared mailboxes, and public folders. Each of these options has a different purpose, user experience, and feature set. What to use depends on what the user needs to do and which tools your organization provides. - -## Summary of collaboration options --This table explains the various collaboration options available to you. --|**Collaboration tool**|**Description**| -|:--|:--| -|Groups in Outlook <br/> |A shared workspace that works across all applications in Microsoft 365. Includes a shared inbox, calendar, and OneDrive for Business site for storing files. Users can create, find, and join Groups in Outlook right from their email or calendar. New and existing users with an Exchange Online or a Microsoft 365 subscription can use Groups in Outlook. <br/> | -|Shared mailbox <br/> |A mailbox for select users to read and send email messages and share a common calendar. Shared mailboxes also can serve as a generic email address (such as info@contoso.com or sales@contoso.com) that customers can use to inquire about your company. When the Send As permission is enabled on the shared mailbox, email sent from the mailbox will use the generic address (e.g., sales@contoso.com). <br/> | -|Distribution list (also called distribution group) <br/> |Used to distribute email messages to two or more people at the same time. Distribution groups are also known as mail-enabled distribution groups. A variant of the distribution group, called the dynamic distribution group, is a mail-enabled Active Directory group object used to send email to a large and evolving group of recipients. The exact recipients are determined by filters and conditions that you specify, such as all members of a particular locale or all full-time employees. <br/><br/> Microsoft 365 Groups in Outlook offer a more powerful solution for collaboration than distribution groups. To learn more, see [Why you should upgrade your distribution lists to groups in Outlook](https://support.microsoft.com/office/7fb3d880-593b-4909-aafa-950dd50ce188) and [Migrate distribution lists to Microsoft 365 Groups](../manage/upgrade-distribution-lists.md). <br/> | -|Public folder <br/> |Designed for shared access, public folders provide an easy and effective way to collect, organize, and share information with other people in your organization. Public folders organize content in a deep hierarchy that's easy to browse and always visible in the Outlook folder view. A public folder can be mail-enabled and added as a member of the distribution group. Email sent to the distribution group is automatically added to the public folder for archiving or later reference. Public folders also provide simple document sharing when you don't have a SharePoint Online subscription. <br/> | - -## Which collaboration tool to use? --The following table gives you a quick glance at the various types of groups and explains when and how to use them with the various collaboration features. - --||**Groups in Outlook**|**Distribution lists**|**Shared mailboxes**|**Public folders**| -|:--|:--|:--|:--|:--| -|**Who uses?** <br/> |Users who want a collaboration workspace for their group messages, files, and calendar that is integrated with the services they already use (Outlook Web App, OneDrive for Business) <br/> |Users who need to send email to a group of recipients with a common interest or characteristic. <br/> |Shared mailboxes are a great way to handle customer email questions because several people in your organization can share the responsibility of monitoring the mailbox and responding to queries. Your customer questions get quicker answers, and related emails are all stored in one mailbox. <br/><br/> Delegates working on behalf of a virtual identity, such as support@contoso.com. Delgates can respond to email as that shared mailbox identity. <br/> |With the proper permissions, everyone in your organization can access and search public folders. They are ideal for email archiving or for sharing documents. <br/> | -|**Ideal group size** <br/> |Any <br/> |Large <br/> |Small <br/> |Large <br/> | -|**Access** <br/> |Exchange Online and users <br/> |For distribution groups, members must be manually added. For dynamic distribution groups, members are added based on filtering criteria. <br/> |Users can be granted Full Access and/or Send As permissions. If granted Full Access permissions, users must also add the shared mailbox to their Outlook profile to access the shared mailbox. <br/> |Accessible by anyone in your organization <br/> | -|**Shared calendar?** <br/> |Yes <br/> |No <br/> |Yes <br/> |Yes <br/> | -|**Email arrives in user's personal Inbox?** <br/> |No. Users can subscribe to a group and then forward all Group messages to their inbox <br/> |Yes. Email arrives in the inbox of all distribution group members. <br/> |No. Email arrives in the Inbox of the shared mailbox. <br/> |No. Email arrives in the public folder. <br/> | -|**Supported clients** <br/> | Outlook 2016 <br/> Outlook 2013 (forward after subscribing) <br/> Outlook Web App <br/> Outlook 2010 (forward after subscribing) <br/> Outlook 2007 (forward after subscribing) <br/> | Outlook 2016 <br/> Outlook 2013 <br/> Outlook Web App <br/> Outlook 2010 <br/> Outlook 2007 <br/> | Outlook 2016 <br/> Outlook 2013 <br/> Outlook Web App <br/> Outlook 2010 <br/> Outlook 2007 <br/> | Outlook 2016 <br/> Outlook 2013 <br/> Outlook Web App <br/> Outlook 2010 <br/> Outlook 2007 <br/> | --## Related content --[Manage distribution groups](/exchange/recipients-in-exchange-online/manage-distribution-groups/manage-distribution-groups) - -[Use Microsoft 365 Groups instead of Site Mailboxes](https://support.microsoft.com/office/737d6b1f-67cc-41fe-8db8-f2d09dd1673b) - -[Create shared mailboxes in Microsoft 365](create-a-shared-mailbox.md) - -[Public folders in Microsoft 365 and Exchange Online](/exchange/collaboration-exo/public-folders/public-folders) |
bookings | Bookings In Outlook | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/bookings/bookings-in-outlook.md | For more information, see the [Bookings with me Microsoft 365 Roadmap item](http ```PowerShell Set-SharingPolicy "Default Sharing Policy" -Domains @{Add="Anonymous:CalendarSharingFreeBusySimple"} ```- - For more information, see [Set-SharingPolicy](/powershell/module/exchange/set-sharingpolicy). +3. For mailboxes that get assigned a customized SharingPolicy, the policy must have Anonymous:SharingPolicyActio as one of the domains. ++ ```Powershell: + get-mailbox adam@contoso.com | Format-List SharingPolicy + ``` ++ If the command returns: ++ `SharingPolicy : "contoso.onmicrosoft.com\Default Sharing (CONTOSO)"` ++ You must update the policy with one of the required domains: ++ ```Powershell + Set-SharingPolicy "Default Sharing (CONTOSO)" -Domains @{Add="Anonymous:CalendarSharingFreeBusySimple"} + ``` ++For more information, see [Set-SharingPolicy](/powershell/module/exchange/set-sharingpolicy). ## Turn Bookings with me on or off |
bookings | Delete Calendar | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/bookings/delete-calendar.md | The booking calendar is where all relevant information about that booking calend ## Delete a booking calendar using Exchange Online PowerShell -See [Connect to Exchange Online PowerShell](/powershell/exchange/exchange-online-powershell-v2) for prerequisites and guidance for connecting to Exchange Online PowerShell. +1. [Connect to Exchange Online PowerShell](/powershell/exchange/connect-to-exchange-online-powershell). -To perform these steps, you must be using an active Microsoft PowerShell command window that you ran by choosing the ΓÇ£Run as administratorΓÇ¥ option. --1. In a PowerShell window, load the EXO V2 module by running the following command: -- ```powershell - Import-Module ExchangeOnlineManagement - ``` -- > [!NOTE] - > If you've already [installed the EXO V2 module](/powershell/exchange/exchange-online-powershell-v2#install-and-maintain-the-exo-v2-module), the previous command will work as written. - -2. The command that you need to run uses the following syntax: -- ```powershell - Connect-ExchangeOnline -UserPrincipalName <UPN> - ``` -- - _\<UPN\>_ is your account in user principal name format (for example, `john@contoso.com`). --3. When you are prompted, log on with tenant administrator credentials to the Microsoft 365 tenant that hosts the booking calendar you want to permanently delete. --4. Once this command is done processing, enter the following command to get a list of the booking mailboxes in your tenant: +2. Run the following command to get a list of the booking mailboxes in your tenant: ```powershell Get-EXOMailbox -RecipientTypeDetails SchedulingMailbox ``` -5. Type the following command: +3. Replace \<BookingCalendarToDelete\> with the exact name of the booking mailbox alias that you want to permanently delete, and then run the following command: ```powershell- remove-mailbox [BookingCalendarToDelete] + Remove-Mailbox -Identity <BookingCalendarToDelete> ``` > [!IMPORTANT] > Be careful to type the exact name of the booking mailbox alias that you want to permanently delete. -6. To verify that the calendar has been deleted, enter the following command: +4. To verify that the calendar has been deleted, run the following command: ```powershell Get-EXOMailbox -RecipientTypeDetails SchedulingMailbox |
compliance | Clone A Content Search | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/clone-a-content-search.md | Why clone Content Searches? ## Script information -- You need to install the Exchange Online V2 module. For instructions, see [Install and maintain the EXO V2 module](/powershell/exchange/exchange-online-powershell-v2#install-and-maintain-the-exo-v2-module).+- You need to install the Exchange Online PowerShell module. For instructions, see [Install and maintain the Exchange Online PowerShell module](/powershell/exchange/exchange-online-powershell-v2#install-and-maintain-the-exchange-online-powershell-module). - You have to be a member of the eDiscovery Manager role group in the Microsoft Purview compliance portal to run the script described in this topic. |
compliance | Communication Compliance Reports Audits | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/communication-compliance-reports-audits.md | Use the *Export* option to create a .csv file containing the report details for - **Policy settings and status**: provides a detailed look at policy configuration and settings, as well as the general status for each of the policy (matches and actions) on messages. Includes policy information and how policies are associated with users and groups, locations, review percentages, reviewers, status, and when the policy was last modified. Use the *Export* option to create a .csv file containing the report details. - **Items and actions per policy**: Review and export matching items and remediation actions per policy. Includes policy information and how policies are associated with: - - Items matched - - Escalated items - - Resolved items - - Tagged as compliant - - Tagged as non-compliant - - Tagged as questionable - - Items pending review - - User notified - - Case created + - Items matched + - Escalated items + - Resolved items + - Tagged as compliant + - Tagged as non-compliant + - Tagged as questionable + - Items pending review + - User notified + - Case created - **Item and actions per location**: Review and export matching items and remediation actions per Microsoft 365 location. Includes information about how workload platforms are associated with: - - Items matched - - Escalated items - - Resolved items - - Tagged as compliant - - Tagged as non-compliant - - Tagged as questionable - - Items pending review - - User notified - - Case created + - Items matched + - Escalated items + - Resolved items + - Tagged as compliant + - Tagged as non-compliant + - Tagged as questionable + - Items pending review + - User notified + - Case created - **Activity by user**: Review and export matching items and remediation actions per user. Includes information about how users are associated with: - - Items matched - - Escalated items - - Resolved items - - Tagged as compliant - - Tagged as non-compliant - - Tagged as questionable - - Items pending review - - User notified - - Case created + - Items matched + - Escalated items + - Resolved items + - Tagged as compliant + - Tagged as non-compliant + - Tagged as questionable + - Items pending review + - User notified + - Case created - **Sensitive information type per location** (preview): Review and export information about the detection of sensitive information types and the associated sources in communication compliance policies. Includes the overall total and the specific breakdown of sensitive information type instances in the sources configured in your organization. The values for each third-party source are displayed in separate columns in the .csv file. Examples are: - - **Email**: Sensitive information types detected in Exchange email messages. - - **Teams**: Sensitive information types detected in Microsoft Teams channels and chat messages. - - **Yammer**: Sensitive information types detected in Yammer inboxes, posts, chats, and replies. - - **Third-party sources**: Sensitive information types detected for activities associated with third-party connectors configured in your organization. To view the breakdown of third-party sources for a specific sensitive information type in the report, hover your mouse over the value for the sensitive information type in the Third-party source column. - - **Other**: Sensitive information types used for internal system processing. Selecting or deselecting this source for the report won't affect any values. + - **Email**: Sensitive information types detected in Exchange email messages. + - **Teams**: Sensitive information types detected in Microsoft Teams channels and chat messages. + - **Yammer**: Sensitive information types detected in Yammer inboxes, posts, chats, and replies. + - **Third-party sources**: Sensitive information types detected for activities associated with third-party connectors configured in your organization. To view the breakdown of third-party sources for a specific sensitive information type in the report, hover your mouse over the value for the sensitive information type in the Third-party source column. + - **Other**: Sensitive information types used for internal system processing. Selecting or deselecting this source for the report won't affect any values. ### Message details report In some instances, you must provide information to regulatory or compliance audi To view communication compliance policy update activities, select the **Export policy updates** control on the main page for any policy. You must be assigned the *Global Admin* or *Communication Compliance Admin* roles to export update activities. This action generates an audit file in the .csv format that contains the following information: -|**Field**|**Details**| -|:--|:--| +|Field|Details| +||| | **CreationDate** | The date the update activity was performed in a policy. | | **UserIds** | The user that performed the update activity in a policy. | | **Operations** | The update operations performed on the policy. | To view communication compliance policy update activities, select the **Export p To view communication compliance review activities for a policy, select the **Export review activities** control on the **Overview** page for a specific policy. You must be assigned the *Global Admin* or *Communication Compliance Admin* roles to export review activities. This action generates an audit file in the .csv format that contains the following information: -|**Field**|**Details**| -|:--|:--| +|Field|Details| +||| | **CreationDate** | The date the review activity was performed in a policy. | | **UserIds** | The user that performed the review activity in a policy. | | **Operations** | The review operations performed on the policy. | Communication compliance policy matches are stored in a supervision mailbox for To check the size of a supervision mailbox for a policy, complete the following steps: -1. Use the [Connect-ExchangeOnline](/powershell/module/exchange/connect-exchangeonline) cmdlet in the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell using modern authentication. -2. Run the following command in PowerShell: +1. [Connect to Exchange Online PowerShell](/powershell/exchange/connect-to-exchange-online-powershell). +2. Run the following command: ```PowerShell ForEach ($p in Get-SupervisoryReviewPolicyV2 | Sort-Object Name) |
compliance | Compliance Manager Mcca | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/compliance-manager-mcca.md | Certain user roles are required to access and use CAMP, and to access informatio You can install the CAMP tool using Windows PowerShell. Once you download and install the tool, you don't need to repeat those steps in order to run reports. Each time you open CAMP, it will ask you for you to log in, and it will generate a new, updated report. -### Step 1: Install the Exchange Online PowerShell V2 module +### Step 1: Install the Exchange Online PowerShell module -To begin, you'll need the Exchange Online PowerShell module (v2.0.3 or higher) that's available in the PowerShell gallery. For installation instructions, see [Install and maintain the EXO V2 module](/powershell/exchange/exchange-online-powershell-v2#install-and-maintain-the-exo-v2-module). +To begin, you'll need the Exchange Online PowerShell module (v2.0.3 or higher) that's available in the PowerShell gallery. For installation instructions, see [Install and maintain the Exchange Online PowerShell module](/powershell/exchange/exchange-online-powershell-v2#install-and-maintain-the-exchange-online-powershell-module). ### Step 2: Install CAMP |
compliance | Disposition | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/disposition.md | Use the **Disposition** page from **Records Management** in the Microsoft Purvie ## Prerequisites for viewing content dispositions -To manage disposition reviews and confirm that records have been deleted, you must have sufficient permissions and auditing must be enabled. Also be aware of any [limitations](retention-limits.md#maximum-number-of-items-for-disposition) for disposition. +To manage disposition reviews and confirm that records have been deleted, you must have sufficient permissions and auditing must be enabled. Also be aware of any [limitations](retention-limits.md#maximum-numbers-for-disposition) for disposition. ### Permissions for disposition |
compliance | Get Started Core Ediscovery | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/get-started-core-ediscovery.md | Licensing for eDiscovery (Standard) requires the appropriate organization subscr - A Microsoft 365 E3 or Office 365 E3 license or higher OR+ + - Microsoft 365 Business Premium (Exchange only) license + ++ OR - Office 365 E1 license with an Exchange Online Plan 2 or Exchange Online Archiving add-on license |
compliance | Migrate Legacy Ediscovery Searches And Holds | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/migrate-legacy-eDiscovery-searches-and-holds.md | To help customers take advantage of the new and improved functionality, this art ## Before you begin -- You need to install the Exchange Online V2 module. For instructions, see [Install and maintain the EXO V2 module](/powershell/exchange/exchange-online-powershell-v2#install-and-maintain-the-exo-v2-module).+- You need to install the Exchange Online PowerShell module. For instructions, see [Install and maintain the Exchange Online PowerShell module](/powershell/exchange/exchange-online-powershell-v2#install-and-maintain-the-exchange-online-powershell-module). - You have to be a member of the eDiscovery Manager role group in the compliance portal to run the PowerShell commands described in this article. You also have to be a member of the Discovery Management role group in the <a href="https://go.microsoft.com/fwlink/p/?linkid=2059104" target="_blank">Exchange admin center</a>. |
compliance | Ome Message Access Logs | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/ome-message-access-logs.md | Access logs are available for encrypted messages through the encrypted message p ## Enabling message access audit logs in PowerShell -Access log can be enabled using [Exchange Online PowerShell V2 module](/powershell/exchange/connect-to-exchange-online-powershell?view=exchange-ps). The *-EnablePortalTrackingLogs* parameter of Set-IrmConfiguration specifies whether to enable the audit logs of accessing the encrypted message portal. Valid values are: +Access log can be enabled using [Exchange Online PowerShell](/powershell/exchange/connect-to-exchange-online-powershell). The *EnablePortalTrackingLogs* parameter of the **[Set-IrmConfiguration](/powershell/module/exchange/set-irmconfiguration)** cmdlet specifies whether to enable the audit logs of accessing the encrypted message portal. Valid values are: - $true: Turn on audit feature. - $false: Turn off audit feature |
compliance | Permissions Filtering For Content Search | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/permissions-filtering-for-content-search.md | f1.keywords: Previously updated : Last updated : audience: Admin ms.localizationpriority: medium-+ - Strat_O365_IP - M365-security-compliance - SPO_Content+search.appverid: - MOE150 - MET150 ms.assetid: 1adffc35-38e5-4f7d-8495-8e0e8721f377 You can use search permissions filtering to let an eDiscovery manager search onl Search permissions filters are applied when you search for content using Content search, Microsoft Purview eDiscovery (Standard), and Microsoft Purview eDiscovery (Premium) in the Microsoft Purview compliance portal. When a search permissions filter is applied to a specific user, that user can perform the following search-related actions: - Search for content- - Preview search results- - Export search results- - Purge items returned by a search -You can also use search permissions filtering to create logical boundaries (called *compliance boundaries*) within an organization that control the user content locations (such as mailboxes, SharePoint sites, and OneDrive accounts) that specific eDiscovery managers can search. For more information, see [Set up compliance boundaries for eDiscovery investigations](set-up-compliance-boundaries.md). - -The following four cmdlets in Security & Compliance PowerShell let you configure and manage search permissions filters: - -[New-ComplianceSecurityFilter](#new-compliancesecurityfilter) --[Get-ComplianceSecurityFilter](#get-compliancesecurityfilter) +You can also use search permissions filtering to create logical boundaries (called _compliance boundaries_) within an organization that control the user content locations (such as mailboxes, SharePoint sites, and OneDrive accounts) that specific eDiscovery managers can search. For more information, see [Set up compliance boundaries for eDiscovery investigations](set-up-compliance-boundaries.md). -[Set-ComplianceSecurityFilter](#set-compliancesecurityfilter) +The following four cmdlets in Security & Compliance PowerShell let you configure and manage search permissions filters: -[Remove-ComplianceSecurityFilter](#remove-compliancesecurityfilter) +- [New-ComplianceSecurityFilter](#new-compliancesecurityfilter) +- [Get-ComplianceSecurityFilter](#get-compliancesecurityfilter) +- [Set-ComplianceSecurityFilter](#set-compliancesecurityfilter) +- [Remove-ComplianceSecurityFilter](#remove-compliancesecurityfilter) ## Requirements to configure permissions filtering The following four cmdlets in Security & Compliance PowerShell let you configure ## Connect to Exchange Online and Security & Compliance PowerShell in a single session -Before you can successfully run the script in this section, you have to download and install the Exchange Online PowerShell V2 module. For information, see [About the Exchange Online PowerShell V2 module](/powershell/exchange/exchange-online-powershell-v2#install-and-maintain-the-exo-v2-module). +Before you can successfully run the script in this section, you have to download and install the Exchange Online PowerShell module. For information, see [Install and maintain the Exchange Online Powershell module](/powershell/exchange/exchange-online-powershell-v2#install-and-maintain-the-exchange-online-powershell-module). 1. Save the following text to a Windows PowerShell script file by using a filename suffix of **.ps1**. For example, you could save it to a file named **ConnectEXO-SCC.ps1**. Before you can successfully run the script in this section, you have to download $UserCredential = Get-Credential Connect-ExchangeOnline -Credential $UserCredential -ShowBanner:$false Connect-IPPSSession -Credential $UserCredential- $Host.UI.RawUI.WindowTitle = $UserCredential.UserName + " (Exchange Online + Compliance Center)" + $Host.UI.RawUI.WindowTitle = $UserCredential.UserName + " (Exchange Online + Security & Compliance)" ``` 2. On your local computer, open Windows PowerShell, go to the folder where the script that you created in the previous step is located, and then run the script; for example: For troubleshooting PowerShell connection errors, see: ## New-ComplianceSecurityFilter -The **New-ComplianceSecurityFilter** is used to create a search permissions filter. Here's the basic syntax for this cmdlet: +The **New-ComplianceSecurityFilter** cmdlet is used to create a search permissions filter. Here's the basic syntax for this cmdlet: ```powershell New-ComplianceSecurityFilter -FilterName <name of filter> -Users <user or role group> -Filters <filter> New-ComplianceSecurityFilter -FilterName <name of filter> -Users <user or role g The following sections describe the parameters for this cmdlet. All parameters are required to create a search permissions filter. -### *FilterName* +### FilterName The _FilterName_ parameter specifies the name of the permissions filter. This name is used to identity a filter when using the **Get-ComplianceSecurityFilter**, **Set-ComplianceSecurityFilter,** and **Remove-ComplianceSecurityFilter** cmdlets. -### *Filters* +### Filters -The _Filters_ parameter specifies the search criteria for the compliance security filter. You can create three different types of filters: +The _Filters_ parameter specifies the search criteria for the compliance security filter. You can create three different types of filters: -- **Mailbox or OneDrive filtering:** This type of filter specifies the mailboxes and OneDrive accounts the assigned users (specified by the _Users_ parameter) can search. This type of filter is called a *content location* filter because it defines the content locations that a user can search. The syntax for this type of filter is **Mailbox_** _MailboxPropertyName_, where _MailboxPropertyName_ specifies a mailbox property used to scope the mailboxes and OneDrive accounts that can be searched. For example, the mailbox filter `"Mailbox_CustomAttribute10 -eq 'OttawaUsers'"` would allow the user assigned this filter to search only the mailboxes and OneDrive accounts that have the value "OttawaUsers" in the CustomAttribute10 property.+- **Mailbox or OneDrive filtering:** This type of filter specifies the mailboxes and OneDrive accounts the assigned users (specified by the _Users_ parameter) can search. This type of filter is called a _content location_ filter because it defines the content locations that a user can search. The syntax for this type of filter is **Mailbox_** _MailboxPropertyName_, where _MailboxPropertyName_ specifies a mailbox property used to scope the mailboxes and OneDrive accounts that can be searched. For example, the mailbox filter `"Mailbox_CustomAttribute10 -eq 'OttawaUsers'"` would allow the user assigned this filter to search only the mailboxes and OneDrive accounts that have the value "OttawaUsers" in the CustomAttribute10 property. Any supported filterable recipient property can be used for the _MailboxPropertyName_ property in a mailbox or OneDrive filter. The following table list four commonly used recipient properties used to create a mailbox or OneDrive filter. The table also includes an example of using the property in a filter. - |Property name |Example | - ||| - |Alias |`"Mailbox_Alias -like 'v-'"` | - |Company |`"Mailbox_Company -eq 'Contoso'"` | - |CountryOrRegion |`"Mailbox_CountryOrRegion -eq 'United States'"` | - |Department |`"Mailbox_Department -eq 'Finance'"` | - ||| + |Property name|Example| + ||| + |Alias|`"Mailbox_Alias -like 'v-'"`| + |Company|`"Mailbox_Company -eq 'Contoso'"`| + |CountryOrRegion|`"Mailbox_CountryOrRegion -eq 'United States'"`| + |Department|`"Mailbox_Department -eq 'Finance'"`| -- **Mailbox content filtering:** This type of filter is applied on the content that can be searched. This type of filter is called a *content filter* because it specifies the mailbox content or searchable email properties the assigned users can search for. The syntax for this type of filter is **MailboxContent_**_SearchablePropertyName, where _SearchablePropertyName_ specifies a Keyword Query Language (KQL) property that can be specified in a search. For example, the mailbox content filter `"MailboxContent_Recipients -like 'contoso.com'"` would allow the user assigned this filter to only search for messages sent to recipients in the contoso.com domain. For a list of searchable email properties, see [Keyword queries and search conditions for eDiscovery](keyword-queries-and-search-conditions.md#searchable-email-properties).+- **Mailbox content filtering:** This type of filter is applied on the content that can be searched. This type of filter is called a _content filter_ because it specifies the mailbox content or searchable email properties the assigned users can search for. The syntax for this type of filter is **MailboxContent_**_SearchablePropertyName_, where _SearchablePropertyName_ specifies a Keyword Query Language (KQL) property that can be specified in a search. For example, the mailbox content filter `"MailboxContent_Recipients -like 'contoso.com'"` would allow the user assigned this filter to only search for messages sent to recipients in the contoso.com domain. For a list of searchable email properties, see [Keyword queries and search conditions for eDiscovery](keyword-queries-and-search-conditions.md#searchable-email-properties). > [!IMPORTANT] > A single search filter can't contain a mailbox filter and a mailbox content filter. To combine these in a single filter, you have to use a [filters list](#using-a-filters-list-to-combine-filter-types). But a filter can contain a more complex query of the same type. For example, `"Mailbox_CustomAttribute10 -eq 'FTE' -and Mailbox_MemberOfGroup -eq '$($DG.DistinguishedName)'"` The _Filters_ parameter specifies the search criteria for the compliance securi - **Site and site content filtering:** There are two SharePoint- and OneDrive-related filters that you can use to specify what site or site content the assigned users can search. - **Site_**_SearchableSiteProperty_- + - **SiteContent_**_SearchableSiteProperty_- - These two filters are interchangeable. For example, `"Site_Path -like 'https://contoso.sharepoint.com/sites/doctors'"` and `"SiteContent_Path -like 'https://contoso.sharepoint.com/sites/doctors'"` return the same results. For a list of searchable site properties, see [Keyword queries and search conditions for eDiscovery](keyword-queries-and-search-conditions.md#searchable-site-properties) For a more complete list, see [Overview of crawled and managed properties in SharePoint](/SharePoint/technical-reference/crawled-and-managed-properties-overview). Properties marked with a **Yes** in the **Queryable** column can be used to create a site or site content filter. ++ These two filters are interchangeable. For example, `"Site_Path -like 'https://contoso.sharepoint.com/sites/doctors'"` and `"SiteContent_Path -like 'https://contoso.sharepoint.com/sites/doctors'"` return the same results. For a list of searchable site properties, see [Keyword queries and search conditions for eDiscovery](keyword-queries-and-search-conditions.md#searchable-site-properties) For a more complete list, see [Overview of crawled and managed properties in SharePoint](/SharePoint/technical-reference/crawled-and-managed-properties-overview). Properties marked with a **Yes** in the **Queryable** column can be used to create a site or site content filter. > [!IMPORTANT] > Setting up a site filter with one of the supported properties doesn't mean the site property in the filter will propagate to all documents on that site. This means the user is still responsible for populating the specific property fields associated with the documents on that site in order for the site filter to work and capture the right content. For example, if the user has a security filter "Site_RefineableString00 -eq 'abc'" applied and then the user runs a search using keyword query "xyz". The security filter gets appended to the query and the actual query running would be "xyz **AND RefineableString0:'abc'**". The user needs to ensure that documents on the site indeed have values in the RefineableString00 field as"abc". If not, the search query won't return any results. -Keep the following considerations in mind when configuring the *Filters* parameter for search permissions filters: +Keep the following considerations in mind when configuring the _Filters_ parameter for search permissions filters: -- Unlike mailboxes, there isn't a content location filter for sites even though the *Site* filter looks like a location filter. All filters for SharePoint and OneDrive are content filters (which is also why *Site_* and *SiteContent_* filters are interchangeable) because site-related properties like *Path* are stamped directly on the documents. Why is this? It's a result of the way that SharePoint is designed. In SharePoint, there isn't a "site object" with properties, like there is with Exchange mailboxes. Therefore, the *Path* property is stamped on the document and contains the URL of the site where the document is located. This is why a *Site* filter is considered a content filter and not a content location filter.+- Unlike mailboxes, there isn't a content location filter for sites even though the _Site_ filter looks like a location filter. All filters for SharePoint and OneDrive are content filters (which is also why _Site\__ and _SiteContent\__ filters are interchangeable) because site-related properties like _Path_ are stamped directly on the documents. Why is this? It's a result of the way that SharePoint is designed. In SharePoint, there isn't a "site object" with properties, like there is with Exchange mailboxes. Therefore, the _Path_ property is stamped on the document and contains the URL of the site where the document is located. This is why a _Site_ filter is considered a content filter and not a content location filter. - You have to create a search permissions filter to explicitly prevent users from searching content locations in a specific service (such as preventing a user from searching any Exchange mailbox or any SharePoint site). In other words, creating a search permissions filter that allows a user to search all SharePoint sites in the organization doesn't prevent that user from searching mailboxes. For example, to allow SharePoint admins to only search SharePoint sites, you have to create a filter that prevents them from searching mailboxes. Similarly, to allow Exchange admins to only search mailboxes, you have to create a filter that prevents them from searching sites. -### *Users* +### Users The _Users_ parameter specifies the users who get this filter applied to their searches. Identify users by their alias or primary SMTP address. You can specify multiple values separated by commas, or you can assign the filter to all users by using the value **All**. You can also use the _Users_ parameter to specify a compliance portal role grou ### Using a filters list to combine filter types -A *filters list* is a filter that includes a mailbox filter and a site filter separated by a comma. This comma also functions as an **OR** operator. Using a filters list is the only supported method for combining different types of filters. In the following example, notice that a comma separates the **Mailbox** and **Site** filters: +A _filters list_ is a filter that includes a mailbox filter and a site filter separated by a comma. This comma also functions as an **OR** operator. Using a filters list is the only supported method for combining different types of filters. In the following example, notice that a comma separates the **Mailbox** and **Site** filters: ```powershell -Filters "Mailbox_CustomAttribute10 -eq 'OttawaUsers'", "SiteContent_Path -like 'https://contoso.sharepoint.com/sites/doctors'" Keep the following things in mind about using a filters list: Here are examples of using the **New-ComplianceSecurityFilter** cmdlet to create a search permissions filter. This example allows members of the "US Discovery Managers" role group to search only the mailboxes and OneDrive accounts in the United States.- + ```powershell New-ComplianceSecurityFilter -FilterName USDiscoveryManagers -Users "US Discovery Managers" -Filters "Mailbox_CountryOrRegion -eq 'United States'" ```- + This example allows the user annb@contoso.com to perform search actions only for mailboxes and OneDrive accounts in Canada. This filter contains the three-digit numeric country code for Canada from ISO 3166-1. ```powershell New-ComplianceSecurityFilter -FilterName "Fourth Coffee Security Filter" -Users > In the previous example, an additional site content filter (`SiteContent_Path -like 'https://contoso-my.sharepoint.com/personal'`) has to be included so that role group members can search for documents in OneDrive accounts. If this filter isn't included, the the filter would only allow role group members to search for documents located in `https://contoso.sharepoint.com/sites/FourthCoffee`. This example allows members of the eDiscovery Manager role group to search only the mailboxes and OneDrive accounts of members of the Ottawa Users distribution group. The Get-DistributionGroup cmdlet in Exchange Online PowerShell is used to find the members of the Ottawa Users group.- + ```powershell $DG = Get-DistributionGroup "Ottawa Users" ``` $DG = Get-DistributionGroup "Executive Team" ``` ```powershell-New-ComplianceSecurityFilter -FilterName NoExecutivesPreview -Users All -Filters "Mailbox_MemberOfGroup -ne '$($DG.DistinguishedName)'" +New-ComplianceSecurityFilter -FilterName NoExecutivesPreview -Users All -Filters "Mailbox_MemberOfGroup -ne '$($DG.DistinguishedName)'" ``` This example allows members of the OneDrive eDiscovery Managers custom role group to only search for content in OneDrive accounts in the organization. This example allows members of the OneDrive eDiscovery Managers custom role grou ```powershell New-ComplianceSecurityFilter -FilterName OneDriveOnly -Users "OneDrive eDiscovery Managers" -Filters "SiteContent_Path -like 'https://contoso-my.sharepoint.com/personal'" ```- + This example restricts the user to performing search actions only on email messages sent during the calendar year 2015. ```powershell New-ComplianceSecurityFilter -FilterName EmailDateRestrictionFilter -Users donh@ Similar to the previous example, this example restricts the user to performing search actions only on documents that were last changed sometime in the calendar year 2015. ```powershell-New-ComplianceSecurityFilter -FilterName DocumentDateRestrictionFilter -Users donh@contoso.com -Filters "SiteContent_LastModifiedTime -ge '01-01-2015' -and SiteContent_LastModifiedTime -le '12-31-2015'" +New-ComplianceSecurityFilter -FilterName DocumentDateRestrictionFilter -Users donh@contoso.com -Filters "SiteContent_LastModifiedTime -ge '01-01-2015' -and SiteContent_LastModifiedTime -le '12-31-2015'" ``` This example prevents members of the "OneDrive Discovery Managers" role group from performing search actions on any mailbox in the organization. New-ComplianceSecurityFilter -FilterName "Coho Winery Security Filter" -Users "C ## Get-ComplianceSecurityFilter The **Get-ComplianceSecurityFilter** is used to return a list of search permissions filters. Use the _FilterName_ parameter to return information for a specific search filter.- + ## Set-ComplianceSecurityFilter The **Set-ComplianceSecurityFilter** is used to modify an existing search permissions filter. The following sections describe the parameters for this cmdlet. The only required parameter is _FilterName_.- -### *FilterName* ++### FilterName The _FilterName_ parameter specifies the name of the permissions filter. -### *Users* +### Users The _Users_ parameter specifies the users who get this filter applied to their searches. Because this is a multi-value property, specifying a user or group of users with this parameter overwrite the existing list of users. See the following examples for the syntax to add and remove selected users. You can also use the _Users_ parameter to specify a compliance portal role group. This lets you create a custom role group and then assign that role group a search permissions filter. For example, let's say you have a custom role group for eDiscovery managers for the U.S. subsidiary of a multi-national corporation. You can use the _Users_ parameter to specify this role group (by using the Name property of the role group) and then use the _Filter_ parameter to allow only mailboxes in the U.S. to be searched. You can't specify distribution groups with this parameter. -### *Filters* +### Filters The _Filters_ parameter specifies the search criteria for the compliance security filter. You can create three different types of filters: The _Filters_ parameter specifies the search criteria for the compliance securi - **Site and site content filtering:** There are two SharePoint and OneDrive for Business site-related filters that you can use to specify what site or site content the assigned users can search: - - **Site_** *SearchableSiteProperty* - - **SiteContent**_*SearchableSiteProperty* - - These two filters are interchangeable. For example, `"Site_Path -like 'https://contoso.spoppe.com/sites/doctors*'"` and `"SiteContent_Path -like 'https://contoso.spoppe.com/sites/doctors*'"` return the same results. For a list of searchable site properties, see [Overview of crawled and managed properties in SharePoint](/SharePoint/technical-reference/crawled-and-managed-properties-overview). Properties marked with a **Yes** in the **Queryable** column can be used to create a site or site content filter. + - **Site\_** _SearchableSiteProperty_ + - **SiteContent\_**_SearchableSiteProperty_ ++ These two filters are interchangeable. For example, `"Site_Path -like 'https://contoso.spoppe.com/sites/doctors*'"` and `"SiteContent_Path -like 'https://contoso.spoppe.com/sites/doctors*'"` return the same results. For a list of searchable site properties, see [Overview of crawled and managed properties in SharePoint](/SharePoint/technical-reference/crawled-and-managed-properties-overview). Properties marked with a **Yes** in the **Queryable** column can be used to create a site or site content filter. ### Examples of changing search permissions filters These examples show how to use the **Get-ComplianceSecurityFilter** and **Set-ComplianceSecurityFilter** cmdlets to add or remove a user to the existing list of users that the filter is assigned to. When you add or remove users from a filter, specify the user by using their SMTP address.- + This example adds a user to the filter. ```powershell Set-ComplianceSecurityFilter -FilterName OttawaUsersFilter -Users $filterusers.u ## Remove-ComplianceSecurityFilter The **Remove-ComplianceSecurityFilter** is used to delete a search filter. Use the _FilterName_ parameter to specify the filter you want to delete.- + ## More information - **How does search permissions filtering work?** The permissions filter is appended to the search query when a search is run. The permissions filter is joined to the search query by the **AND** Boolean operator. The query logic for the search query and the permissions filter would look like this: The **Remove-ComplianceSecurityFilter** is used to delete a search filter. Use t <SearchQuery> AND <PermissionsFilter> ``` - For example, you have a permissions filter that allows Bob to perform all search actions on the mailboxes of members of the Workers distribution group. Then Bob runs a search on all mailboxes in the organization with the search query `sender:jerry@adatum.com`. Because the permissions filter and the search query are logically combined by an **AND** operator, the search returns any message sent by jerry@adatum.com to any member of the Workers distribution group. + For example, you have a permissions filter that allows Bob to perform all search actions on the mailboxes of members of the Workers distribution group. Then Bob runs a search on all mailboxes in the organization with the search query `sender:jerry@adatum.com`. Because the permissions filter and the search query are logically combined by an **AND** operator, the search returns any message sent by jerry@adatum.com to any member of the Workers distribution group. - **What happens if you have multiple search permissions filters?** In a search query, multiple permissions filters are combined by **OR** Boolean operators. So results will be returned if any of the filters are true. In a search, all filters (combined by **OR** operators) are then combined with the search query by the **AND** operator. The **Remove-ComplianceSecurityFilter** is used to delete a search filter. Use t Let's take the previous example, where a search filter allows Bob to search only the mailboxes of the members of the Workers distribution group. Then we create another filter that prevents Bob from searching Phil's mailbox ("Mailbox_Alias -ne 'Phil'"). And let's also assume that Phil is a member of the Workers group. When Bob runs a search (from the previous example) on all mailboxes in the organization, search results are returned for Phil's mailbox even though you applied filter to prevent Bob from searching Phil's mailbox. This is because the first filter, which allows Bob to search the Workers group, is true. And because Phil is a member of the Workers group, Bob can search Phil's mailbox. - **Does search permissions filtering work for inactive mailboxes?** Yes, you can use mailbox and mailbox content filters to limit who can search inactive mailboxes in your organization. Like a regular mailbox, an inactive mailbox has to be configured with the recipient property that's used to create a permissions filter. If necessary, you can use the **Get-Mailbox -InactiveMailboxOnly** command to display the properties of inactive mailboxes. For more information, see [Create and manage inactive mailboxes](create-and-manage-inactive-mailboxes.md).- + - **Does search permissions filtering work for public folders?** No. As previously explained, search permissions filtering can't be used to limit who can search public folders in Exchange. For example, items in public folder locations can't be excluded from the search results by a permissions filter. - **Does allowing a user to search all content locations in a specific service also prevent them from searching content locations in a different service?** No. As previously explained, you have to create a search permissions filter to explicitly prevent users from searching content locations in a specific service (such as preventing a user from searching any Exchange mailbox or any SharePoint site). In other words, creating a search permissions filter that allows a user to search all SharePoint sites in the organization doesn't prevent that user from searching mailboxes. For example, to allow SharePoint admins to only search SharePoint sites, you have to create a filter that prevents them from searching mailboxes. Similarly, to allow Exchange admins to only search mailboxes, you have to create a filter that prevents them from searching sites. The **Remove-ComplianceSecurityFilter** is used to delete a search filter. Use t - **Do search permissions filters count against search query character limits?** Yes. Search permissions filters count against the character limit for search queries. For more information, see [Limits in eDiscovery (Premium)](limits-ediscovery20.md). **What is the maximum number of search permissions filters that can be created in an organization?**- + There is no limit to the number of search permissions filters that can be created in an organization. However, a search query can have a maximum of 100 conditions. In this case, a condition is defined as something that's connected to the query by a Boolean operator (such as **AND**, **OR**, and **NEAR**). The limit of the number of conditions includes the search query itself plus all search permissions filters that are applied to the user who runs the search. Therefore, the more search permissions filters you have (especially if these filters are applied to the same user or group of users), the better the chance of exceeding the maximum number of conditions for a search. To understand how this limit works, you need to understand that a search permissions filter is appended to the search query when a search is run. A search permissions filter is joined to the search query by the **AND** Boolean operator. The query logic for the search query and a single search permissions filter would look like this: The query logic for the search query and multiple search permissions filters wou It's possible the search query itself may consist of multiple conditions connected by Boolean operators. Each condition in the search query would also count against the 100-condition limit. -Also, the number of search permissions filters appended to a query depends on the user who is running the search. When a specific user runs a search, the search permissions filters that are applied to the user (which is defined by the *Users* parameter in the filter) are appended to the query. Your organization could have hundreds of search permissions filters, but if more than 100 filters are applied to the same users, then it's likely the 100-condition limit will be exceeded when those users run searches. +Also, the number of search permissions filters appended to a query depends on the user who is running the search. When a specific user runs a search, the search permissions filters that are applied to the user (which is defined by the _Users_ parameter in the filter) are appended to the query. Your organization could have hundreds of search permissions filters, but if more than 100 filters are applied to the same users, then it's likely the 100-condition limit will be exceeded when those users run searches. -There's one more thing to keep in mind about the condition limit. The number of specific SharePoint sites that are included in the search query or search permissions filters also count against this limit. +There's one more thing to keep in mind about the condition limit. The number of specific SharePoint sites that are included in the search query or search permissions filters also count against this limit. To prevent your organization from reaching the conditions limit, keep the number of search permissions filters in your organization to few as possible to meet your business requirements. |
compliance | Retention Limits | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/retention-limits.md | SharePoint example: Because you don't need to retain all SharePoint sites, you must create retention policies that specify the specific sites. Because a retention policy doesn't support more than 100 specified sites, you must create multiple policies for the two retention periods. These retention policies have the maximum number of included sites, so the next new site that needs retaining would require a new retention policy, irrespective of the retention period. -## Maximum number of items for disposition +## Maximum numbers for disposition For the [disposition of content](disposition.md), there are some limits to be aware of: For the [disposition of content](disposition.md), there are some limits to be aw - Proof of disposition for up to seven years after the item was disposed, with a limit of 1,000,000 items per retention label for that period. If you need proof of disposition higher than this limit of 1,000,000 for items that are marked as records, contact [Microsoft Support](../admin/get-help-support.md).++- Maximum number of disposition reviewers: + - 10 reviewers per disposition stage in any combination of individual users and mail-enabled security groups + - 200 reviewers per tenant in any combination of individual users and mail-enabled security groups. Because of this limit, we recommend using mail-enabled security groups whenever possible for larger organizations. + |
compliance | Sensitivity Labels Office Apps | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sensitivity-labels-office-apps.md | The numbers listed are the minimum Office application versions required for each |[Manually apply, change, or remove label](https://support.microsoft.com/en-us/office/apply-sensitivity-labels-to-your-files-and-email-in-office-2f96e7cd-d5a4-403b-8bd7-4cc636bae0f9)| Current Channel: 1910+ <br /><br> Monthly Enterprise Channel: 1910+ <br /><br> Semi-Annual Enterprise Channel: 2002+ | 16.21+ | 2.21+ | 16.0.11231+ | [Yes - opt-in](sensitivity-labels-sharepoint-onedrive-files.md) | |[Multi-language support](create-sensitivity-labels.md#additional-label-settings-with-security--compliance-powershell)| Current Channel: 1910+ <br /><br> Monthly Enterprise Channel: 1910+ <br /><br> Semi-Annual Enterprise Channel: 2002+ | 16.21+ | 2.21+ | 16.0.11231+ | Under review | |[Apply a default label](sensitivity-labels.md#what-label-policies-can-do) to new documents | Current Channel: 1910+ <br /><br> Monthly Enterprise Channel: 1910+ <br /><br> Semi-Annual Enterprise Channel: 2002+ | 16.21+ | 2.21+ | 16.0.11231+ | [Yes - opt-in](sensitivity-labels-sharepoint-onedrive-files.md) |-|[Apply a default label](sensitivity-labels.md#what-label-policies-can-do) to existing documents | Rolling out to Current Channel: 2208+ <br /><br> Monthly Enterprise Channel: Under review <br /><br> Semi-Annual Enterprise Channel: Under review | Rolling out to 16.63+ | Under review | Under review | [Yes - opt-in](sensitivity-labels-sharepoint-onedrive-files.md) | +|[Apply a default label](sensitivity-labels.md#what-label-policies-can-do) to existing documents | Current Channel: 2208+ <br /><br> Monthly Enterprise Channel: 2207+ <br /><br> Semi-Annual Enterprise Channel: Under review | 16.63+ | Under review | Under review | [Yes - opt-in](sensitivity-labels-sharepoint-onedrive-files.md) | |[Require a justification to change a label](sensitivity-labels.md#what-label-policies-can-do) | Current Channel: 1910+ <br /><br> Monthly Enterprise Channel: 1910+ <br /><br> Semi-Annual Enterprise Channel: 2002+ | 16.21+ | 2.21+ | 16.0.11231+ | [Yes - opt-in](sensitivity-labels-sharepoint-onedrive-files.md) | |[Provide help link to a custom help page](sensitivity-labels.md#what-label-policies-can-do) | Current Channel: 1910+ <br /><br> Monthly Enterprise Channel: 1910+ <br /><br> Semi-Annual Enterprise Channel: 2002+ | 16.21+ | 2.21+ | 16.0.11231+ | [Yes - opt-in](sensitivity-labels-sharepoint-onedrive-files.md) | |[Mark the content](sensitivity-labels.md#what-sensitivity-labels-can-do) | Current Channel: 1910+ <br /><br> Monthly Enterprise Channel: 1910+ <br /><br> Semi-Annual Enterprise Channel: 2002+ | 16.21+ | 2.21+ | 16.0.11231+ | [Yes - opt-in](sensitivity-labels-sharepoint-onedrive-files.md) | The numbers listed are the minimum Office application versions required for each |[Apply a sensitivity label to content automatically](apply-sensitivity-label-automatically.md) <br /> - Using trainable classifiers | Current Channel: 2105+ <br /><br> Monthly Enterprise Channel: 2105+ <br /><br> Semi-Annual Enterprise Channel: 2108+ | 16.49+ | Under review | Under review | [Yes - opt-in](sensitivity-labels-sharepoint-onedrive-files.md) | |[Support co-authoring and AutoSave](sensitivity-labels-coauthoring.md) for labeled and encrypted documents | Current Channel: 2107+ <br /><br> Monthly Enterprise Channel: 2107+ <br /><br> Semi-Annual Enterprise Channel: 2202+ | 16.51+ | 2.58+ | 16.0.14931+ | [Yes - opt-in](sensitivity-labels-sharepoint-onedrive-files.md) | |[PDF support](#pdf-support)| Current Channel: 2208+ <br /><br> Monthly Enterprise Channel: 2208+ <br /><br> Semi-Annual Enterprise Channel: Under review| Under review | Under review | Under review | Under review |-|[Sensitivity bar](#sensitivity-bar) and [display label color](#label-colors) | Preview: Rolling out to [Beta Channel](https://office.com/insider) | Preview: Rolling out to [Beta Channel](https://office.com/insider) | Under review | Under review | Under review | +|[Sensitivity bar](#sensitivity-bar) and [display label color](#label-colors) | Preview: Rolling out to [Beta Channel](https://office.com/insider) | Under review | Under review | Under review | Under review | ### Sensitivity label capabilities in Outlook For end user documentation, see [Create protected PDFs from Office files](https: Newly supported in preview for built-in labels in Word, Excel, and PowerPoint, but not yet for Outlook or Office for the web, see the tables in the [capabilities](#support-for-sensitivity-label-capabilities-in-apps) section on this page to identify minimum versions. -For supported apps, sensitivity labels are now displayed in a sensitivity bar, displaying next to the file name on the top window bar. For example: +For the supported apps, sensitivity labels are now displayed in a sensitivity bar, next to the file name on the top window bar. For example:  -Information about the labels and the ability to select or change a label are also integrated into user workflows that includes save and rename, export, share, print, and [convert to PDF](#pdf-support). +Information about the labels and the ability to select or change a label are also integrated into user workflows that includes save and rename, export, share, print, and [convert to PDF](#pdf-support). For more information and example screenshots, see the blog post announcement, [New sensitivity bar in Office for Windows](https://insider.office.com/blog/sensitivity-bar-in-office-for-windows). As part of this high visibility, these labels also support colors. For more information, see the next section. As part of this high visibility, these labels also support colors. For more info > [!IMPORTANT] > If your labeling apps don't support this capability, they don't display the configured label colors. > -> The Azure Information Protection unified labeling client supports label colors. For labeling built in to Office, label colors are currently supported in preview for Word, Excel, and PowerPoint on Windows and macOS, but not Outlook or Office for the web. For more information, see the tables in the [capabilities](#support-for-sensitivity-label-capabilities-in-apps) section on this page. +> The Azure Information Protection unified labeling client supports label colors. For labeling built in to Office, label colors are currently supported in preview for Word, Excel, and PowerPoint on Windows, but not yet for Outlook, macOS, or Office for the web. For more information, see the tables in the [capabilities](#support-for-sensitivity-label-capabilities-in-apps) section on this page. Newly created labels don't have a color by default. If your labels were [migrated from Azure Information Protection](/azure/information-protection/configure-policy-migrate-labels) or you configured label colors for the Azure Information Protection unified labeling client, these label colors are now displayed in apps that support them. You can also create custom reports with your choice of security information and - [Known issues with automatically applying or recommending sensitivity labels](https://support.office.com/article/known-issues-with-automatically-applying-or-recommending-sensitivity-labels-451698ae-311b-4d28-83aa-a839a66f6efc) - [Create protected PDFs from Office files](https://support.microsoft.com/topic/aba7e367-e482-49e7-b746-a385e48d01e4)---- |
compliance | Sensitivity Labels Sharepoint Default Label | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sensitivity-labels-sharepoint-default-label.md | Summary of outcomes: ## Requirements -- You have [enabled sensitivity labels for Office files in SharePoint and OneDrive](sensitivity-labels-sharepoint-onedrive-files.md).+- You've [created and published](create-sensitivity-labels.md) sensitivity labels, and they're published to the users who will select a default sensitivity label for a SharePoint document library. ++- You've [enabled sensitivity labels for Office files in SharePoint and OneDrive](sensitivity-labels-sharepoint-onedrive-files.md). To check this status, you can run `Get-SPOTenant -EnableAIPIntegration` from the [SharePoint Online Management Shell](/powershell/sharepoint/sharepoint-online/connect-sharepoint-online) to confirm the value is set to true. - [SharePoint Information Rights Management (IRM) is not enabled for the library](set-up-irm-in-sp-admin-center.md#irm-enable-sharepoint-document-libraries-and-lists). This older technology isn't compatible with using a default sensitivity label for a SharePoint document library. If a library is enabled for IRM, you won't be able to select a default sensitivity label. |
compliance | Sensitivity Labels | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sensitivity-labels.md | The ordering of sublabels is used with [automatic labeling](apply-sensitivity-la With sublabels, you can group one or more labels below a parent label that a user sees in an Office app. For example, under Confidential, your organization might use several different labels for specific types of that classification. In this example, the parent label Confidential is simply a text label with no protection settings, and because it has sublabels, it can't be applied to content. Instead, users must choose Confidential to view the sublabels, and then they can choose a sublabel to apply to content. -Sublabels are simply a way to present labels to users in logical groups. Sublabels don't inherit any settings from their parent label. When you publish a sublabel for a user, that user can then apply that sublabel to content but can't apply just the parent label. +Sublabels are simply a way to present labels to users in logical groups. Sublabels don't inherit any settings from their parent label. When you publish a sublabel for a user, that user can then apply that sublabel to content and containers, but can't apply just the parent label. -Don't choose a parent label as the default label, or configure a parent label to be automatically applied (or recommended). If you do, the parent label won't be applied to content. +Don't choose a parent label as the default label, or configure a parent label to be automatically applied (or recommended). If you do, the parent label can't be applied. Example of how sublabels display for users: |
compliance | Whats New | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/whats-new.md | Whether it be adding new solutions to the [Microsoft Purview compliance portal]( ### Data lifecycle management and records management - [Exchange (legacy)](data-lifecycle-management.md#exchange-legacy-features) configuration is moving from the Classic Exchange admin center (EAC) to the Microsoft Purview compliance portal, under **Data lifecycle management**. Existing data lifecycle management features are located under a new subnode, **Microsoft 365**.-- For cloud attachments (currently rolling out in preview), automatic and temporary retention of deleted files in the Preservation Hold library to safeguard against the original file being deleted by users before the copy can be created and labeled. For more information, see [How retention works with cloud attachements](retention-policies-sharepoint.md#how-retention-works-with-cloud-attachments).+- For cloud attachments (currently rolling out in preview), automatic and temporary retention of deleted files in the Preservation Hold library to safeguard against the original file being deleted by users before the copy can be created and labeled. For more information, see [How retention works with cloud attachments](retention-policies-sharepoint.md#how-retention-works-with-cloud-attachments). ### Data Loss Prevention Whether it be adding new solutions to the [Microsoft Purview compliance portal]( ### Sensitivity labels -- Generally available (GA) and no longer need to opt-in: Mobile devices (iOS and Android, with minimal versions) support [co-authoring for files encrypted with sensitivity labels](sensitivity-labels-coauthoring.md).+- Generally available (GA) and no longer need to opt in: Mobile devices (iOS and Android, with minimal versions) support [co-authoring for files encrypted with sensitivity labels](sensitivity-labels-coauthoring.md). - GA with Current Channel 2208+ for Word, Excel, PowerPoint on Windows: [Support for PDF](sensitivity-labels-office-apps.md#pdf-support). Support for Outlook to block print to PDF when required, is rolling out to Beta Channel. - Rolling out to GA with Current Channel 2208+ for Windows, and 16.63+ for macOS: Default label for existing documents. - In preview: Trainable classifiers for [auto-labeling policies](apply-sensitivity-label-automatically.md). To meet the challenges of today's decentralized, data-rich workplace, we're intr - [Retention policies for Yammer](create-retention-policies.md#retention-policy-for-yammer-locations) are now generally available (GA). - Support for shared channels, currently in preview. When you configure a retention policy for the Teams channel message location, any shared channels inherit retention settings from their parent team.-- [Per-tenant limits for content disposition](retention-limits.md#maximum-number-of-items-for-disposition).+- [Per-tenant limits for content disposition](retention-limits.md#maximum-numbers-for-disposition). ### Data Loss Prevention To meet the challenges of today's decentralized, data-rich workplace, we're intr - [Configure endpoint data loss prevention settings](dlp-configure-endpoint-settings.md) - new for public preview of restricted app groups. - [Data loss prevention policy reference](dlp-policy-reference.md) - updated for public preview of restricted app groups. - [Get started with data loss prevention for Power BI](dlp-powerbi-get-started.md) - new for public preview.-- + ### Information protection - [Support for double byte character set release notes](mip-dbcs-relnotes.md) - added guidance for macOS.-- + ### Insider risk management - [Get started with insider risk management](insider-risk-management-configure.md) - added new tasks for the Recommended actions guidance. |
enterprise | Administering Exchange Online Multi Geo | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/enterprise/administering-exchange-online-multi-geo.md | In Exchange Online multi-geo environments, you don't need to do any manual steps Typically, Exchange Online PowerShell will connect to the central geo location. But, you can also connect directly to satellite geo locations. Because of performance improvements, we recommend connecting directly to the satellite geo location when you only manage users in that location. -The requirements for installing and using the EXO V2 module are described in [Install and maintain the EXO V2 module](/powershell/exchange/exchange-online-powershell-v2#install-and-maintain-the-exo-v2-module). +The requirements for installing and using the Exchange Online PowerShell module are described in [Install and maintain the Exchange Online PowerShell module](/powershell/exchange/exchange-online-powershell-v2#install-and-maintain-the-exchange-online-powershell-module). -To connect Exchange Online PowerShell to a specific geo location, the *ConnectionUri* parameter is different than the regular connection instructions. The rest of the commands and values are the same. +To connect Exchange Online PowerShell to a specific geo location, the _ConnectionUri_ parameter is different than the regular connection instructions. The rest of the commands and values are the same. Specifically, you need to add the `?email=<emailaddress>` value to end of the _ConnectionUri_ value. `<emailaddress>` is the email address of **any** mailbox in the target geo location. Your permissions to that mailbox or the relationship to your credentials are not a factor; the email address simply tells Exchange Online PowerShell where to connect. Microsoft 365 or Microsoft 365 GCC customers typically don't need to use the _Co The following connection instructions work for accounts that are or aren't configured for multi-factor authentication (MFA). -1. In a Windows PowerShell window, load the EXO V2 module by running the following command: +1. In a PowerShell window, load the Exchange Online PowerShell module by running the following command: ```powershell Import-Module ExchangeOnlineManagement |
enterprise | Assign Licenses To User Accounts | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/enterprise/assign-licenses-to-user-accounts.md | Make sure you have enough licenses for all the group members. If you run out of >You should not configure group-based licensing for groups that contain Azure business to business (B2B) accounts. > -For more informaion, see [group-based licensing in Azure AD](/azure/active-directory/fundamentals/active-directory-licensing-whatis-azure-portal). +For more information, see [group-based licensing in Azure AD](/azure/active-directory/fundamentals/active-directory-licensing-whatis-azure-portal). ## Next steps With the appropriate set of user accounts that have been assigned licenses, you are now ready to: -- [Implement security](../security/office-365-security/security-roadmap.md)+- [Implement security](/microsoft-365/security/office-365-security/overview) - [Deploy client software, such as Microsoft 365 Apps](/DeployOffice/deployment-guide-microsoft-365-apps) - [Set up device management](device-management-roadmap-microsoft-365.md)-- [Configure services and applications](configure-services-and-applications.md)+- [Configure services and applications](configure-services-and-applications.md) |
enterprise | Connect To All Microsoft 365 Services In A Single Windows Powershell Window | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/enterprise/connect-to-all-microsoft-365-services-in-a-single-windows-powershell-window.md | Before you can manage all of Microsoft 365 from a single instance of PowerShell, - [Azure Active Directory V2](connect-to-microsoft-365-powershell.md#connect-with-the-azure-active-directory-powershell-for-graph-module) - [SharePoint Online Management Shell](https://go.microsoft.com/fwlink/p/?LinkId=255251) - [Teams PowerShell Module](/microsoftteams/teams-powershell-overview)- - [Exchange Online PowerShell V2](/powershell/exchange/exchange-online-powershell-v2#install-and-maintain-the-exchange-online-powershell-v2-module) + - [Install and maintain the Exchange Online PowerShell module](/powershell/exchange/exchange-online-powershell-v2#install-and-maintain-the-exchange-online-powershell-module) - [Teams PowerShell Overview](/microsoftteams/teams-powershell-overview) - PowerShell must be configured to run signed scripts for Exchange Online, Defender for Office 365, and Microsoft Purview compliance. Run the following command in an elevated PowerShell session (a PowerShell session that you **Run as administrator**). |
enterprise | Contoso Info Protect | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/enterprise/contoso-info-protect.md | Learn how Contoso uses the [security features across Microsoft 365 for enterpris ## See also -[Security roadmap](../security/office-365-security/security-roadmap.md) +[Microsoft Defender for Office 365](/microsoft-365/security/office-365-security/overview) [Microsoft 365 for enterprise overview](microsoft-365-overview.md) |
enterprise | Modern Custom Extensions | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/enterprise/modern-custom-extensions.md | Title: "Optimize custom extensions in SharePoint Online modern site pages" Previously updated : 03/11/2020 Last updated : 09/19/2022 audience: Admin |
enterprise | Use Powershell To Perform An Imap Migration To Microsoft 365 | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/enterprise/use-powershell-to-perform-an-imap-migration-to-microsoft-365.md | Title: "Use PowerShell to perform an IMAP migration to Microsoft 365" Previously updated : 07/17/2020 Last updated : 09/19/2022 audience: Admin |
security | Android Configure Mam | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/security/defender-endpoint/android-configure-mam.md | End users also need to take steps to install Microsoft Defender for Endpoint on - **Create an app protection policy** Block access or wipe data of a managed app based on Microsoft Defender for Endpoint risk signals by creating an app protection policy.-Microsoft Defender for Endpoint can be configured to send threat signals to be used in app protection policies (APP, also known as MAM). With this capability, you can use Microsoft Defender for Endpoint to protect managed apps. +Microsoft Defender for Endpoint can be configured to send threat signals to be used in app protection policies (APP, also known as MAM). With this capability, you can use Microsoft Defender for Endpoint to protect managed apps. 1. Create a policy <br> App protection policies (APP) are rules that ensure an organization's data remains safe or contained in a managed app. A policy can be a rule that is enforced when the user attempts to access or move "corporate" data, or a set of actions that are prohibited or monitored when the user is inside the app. Select **Setting > Max allowed device threat level** in **Device Conditions** an 6. Select **Continue** to log into the managed application. -## Configure privacy controls ->[!IMPORTANT] ->Privacy controls on Microsoft Defender for Endpoint on MAM are in public preview. The following information relates to prereleased product which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here. ->**If you want to try out this feature or provide feedback, please reach out to us at mdatpmobile@microsoft.com.** +## Configure Web protection +Defender for Endpoint on Android allows IT Administrators to configure web protection. Web protection is available within the [Microsoft Endpoint Manager Admin center](https://endpoint.microsoft.com). +Web protection helps to secure devices against web threats and protect users from phishing attacks. Note that anti-phishing and custom indicators (URL and IP addresses) are supported as part of web protection. Web content filtering is currently not supported on mobile platforms. ++1. In the Microsoft Endpoint Manager admin center, go to **Apps > App configuration policies > Add > Managed apps**. ++2. Give the policy a **name**. ++3. Under **Select Public Apps**, choose **Microsoft Defender for Endpoint** as the target app. ++4. In the **Settings** page, under the **General Configuration Settings**, add the following keys and set their value as required. + - **antiphishing** + - **vpn** + + To disable web protection, enter 0 for the antiphishing and VPN values. + To disable only the use of VPN by web protection, enter these values: + - 0 for vpn + - 1 for antiphishing + +1. Add **DefenderMAMConfigs** key and set the value as 1. ++5. Assign this policy to users. By default, this value is set to false. ++6. Review and create the policy. +++## Configure privacy controls Admins can use the following steps to enable privacy and not collect the domain name, app details and network information as part of the alert report for corresponding threats. 1. In Microsoft Endpoint Manager admin center, go to **Apps > App configuration policies > Add > Managed apps**. Admins can use the following steps to enable privacy and not collect the domain 3. Under the Select Public Apps, choose **Microsoft Defender for Endpoint** as the target app. -4. In Settings page, under the General Configuration Settings add **DefenderExcludeURLInReport**, **DefenderExcludeAppInReport** as the keys and value as true. +4. In Settings page, under the General Configuration Settings add **DefenderExcludeURLInReport**, **DefenderExcludeAppInReport** as the keys and value as true. ++1. Add **DefenderMAMConfigs** key and set the value as 1. 5. Assign this policy to users. By default, this value is set to false. 6. Review and create the policy. ## Optional permissions ->[!IMPORTANT] ->Optional Permissions on Microsoft Defender for Endpoint is in public preview. The following information relates to prereleased product which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here. ->**If you want to try out this feature or provide feedback, please reach out to us at mdatpmobile@microsoft.com.** - Microsoft Defender for Endpoint on Android enables Optional Permissions in the onboarding flow. Currently the permissions required by MDE are mandatory in the onboarding flow. With this feature, admin can deploy MDE on Android devices with MAM policies without enforcing the mandatory VPN and Accessibility Permissions during onboarding. End Users can onboard the app without the mandatory permissions and can later review these permissions. ### Configure optional permission Use the following steps to enable Optional permissions for devices. 3. Select **Microsoft Defender for Endpoint*** in public apps. -4. In Settings page, select **Use configuration designer** and add **DefenderOptionalVPN** or **DefenderOptionalAccessibility** or **both** as the key and value type as Boolean. +4. In Settings page, select **Use configuration designer** and **DefenderOptionalVPN** or **DefenderOptionalAccessibility** or **both** as the key and value type as Boolean. ++1. Add **DefenderMAMConfigs** key and set the value as 1. 5. To enable Optional permissions, enter value as **true** and assign this policy to users. By default, this value is set to false. For users with key set as true, the users will be able to onboard the app without giving these permission. |
security | Android Intune | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/security/defender-endpoint/android-intune.md | Follow the steps below to add Microsoft Defender for Endpoint app into your mana - Name: Microsoft Defender for Endpoint. - Choose **Android Enterprise** as platform.- - Choose **Work Profile only** as Profile Type. - - Click **Select App**, choose **Microsoft Defender ATP**, select **OK** and then **Next**. + - Choose **Personally-owned Work Profile only** or **Fully Managed, Dedicated, and Corporate-owned work profile only** as Profile Type. + - Click **Select App**, choose **Microsoft Defender**, select **OK** and then **Next**. :::image type="content" source="images/android-create-app.png" alt-text=" Screenshot of the Associated app details pane." lightbox="images/android-create-app.png"::: Follow the steps below to add Microsoft Defender for Endpoint app into your mana - **Auto grant** - Automatically approves without notifying the user. - **Auto deny** - Automatically denies without notifying the user. - 1. In the **Settings** page, go to the **Configuration settings** section and choose **'Use configuration designer'** in Configuration settings format. + 1. Go to the **Configuration settings** section and choose **'Use configuration designer'** in Configuration settings format. :::image type="content" alt-text="Image of android create app configuration policy." source="images/configurationformat.png" lightbox="images/configurationformat.png"::: Follow the steps below to add Microsoft Defender for Endpoint app into your mana 1. In the **Review + Create** page that comes up next, review all the information and then select **Create**. - The app configuration policy for Defender for Endpoint autogranting the storage permission is now assigned to the selected user group. + The app configuration policy for Defender for Endpoint is now assigned to the selected user group. - > [!div class="mx-imgBorder"] - > :::image type="content" source="images/android-review-create.png" alt-text="The Review + create tab in the Create app configuration policy page" lightbox="images/android-review-create.png"::: -10. Select **Microsoft Defender ATP** app in the list \> **Properties** \> +10. Select **Microsoft Defender** app in the list \> **Properties** \> **Assignments** \> **Edit**. :::image type="content" source="images/mda-properties.png" alt-text="The Edit option on the Properties page" lightbox="images/mda-properties.png"::: |
security | Android Whatsnew | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/security/defender-endpoint/android-whatsnew.md | Want to experience Microsoft Defender for Endpoint? [Sign up for a free trial.]( > > If users can't access the play store, the app can be updated through the company portal. +## Microsoft Defender for Endpoint on Company-owned personally enabled devices +MDE is now generally available on AE COPE devices. Enterprises can onboard devices on COPE mode and push MDE to userΓÇÖs devices through the [Microsoft Endpoint Manager Admin center](https://endpoint.microsoft.com). With this support, Android Enterprise COPE devices will get the full capabilities of our offering on Android including phishing and web protection, malware scanning, Network protection (preview) and additional breach prevention through integration with Microsoft Endpoint Manager and Conditional Access. Read the announcement [here](https://techcommunity.microsoft.com/t5/microsoft-defender-for-endpoint/microsoft-defender-for-endpoint-is-now-available-on-android/ba-p/3626100). + ## Privacy Controls -Microsoft Defender for Endpoint on Android enables Privacy Controls for both the Admins and the End Users. This includes the controls for enrolled (MDM) as well as unenrolled (MAM) devices (in preview). Admins can configure the privacy in the alert report while End Users can configure the information shared to their organization. For more information, see [privacy controls(MDM)](/microsoft-365/security/defender-endpoint/android-configure#privacy-controls) and [privacy controls (MAM)](/microsoft-365/security/defender-endpoint/android-configure-mam#configure-privacy-controls). +Microsoft Defender for Endpoint on Android enables Privacy Controls for both the Admins and the End Users. This includes the controls for enrolled (MDM) as well as unenrolled (MAM) devices. Admins can configure the privacy in the alert report while End Users can configure the information shared to their organization. For more information, see [privacy controls(MDM)](/microsoft-365/security/defender-endpoint/android-configure#privacy-controls) and [privacy controls (MAM)](/microsoft-365/security/defender-endpoint/android-configure-mam#configure-privacy-controls). ## Optional Permissions and Disable Web Protection |
security | Built In Protection | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/security/defender-endpoint/built-in-protection.md | f1.keywords: NOCSH ## What is built-in protection, and how does it work? -Built-in protection is a set of default settings that are rolling out to help ensure your devices are protected. These default settings are designed to protect devices from ransomware and other threats. Initially, built-in protection will include turning [tamper protection](prevent-changes-to-security-settings-with-tamper-protection.md) on for your tenant, with other default settings coming soon. +Built-in protection is a set of default settings that are rolling out to help ensure your devices are protected. These default settings are designed to protect devices from ransomware and other threats. Initially, built-in protection will include turning [tamper protection](prevent-changes-to-security-settings-with-tamper-protection.md) on for your tenant, with other default settings coming soon. For more information, see the Tech Community blog post, [Tamper protection will be turned on for all enterprise customers](https://techcommunity.microsoft.com/t5/microsoft-defender-for-endpoint/tamper-protection-will-be-turned-on-for-all-enterprise-customers/ba-p/3616478). | Phase | What happens | |:|:| Built-in protection is a set of default settings. You aren't required to keep th ## See also +- [Tech Community blog: Tamper protection will be turned on for all enterprise customers](https://techcommunity.microsoft.com/t5/microsoft-defender-for-endpoint/tamper-protection-will-be-turned-on-for-all-enterprise-customers/ba-p/3616478) - [Protect security settings with tamper protection](prevent-changes-to-security-settings-with-tamper-protection.md) - [Manage endpoint security in Microsoft Intune](/mem/intune/protect/endpoint-security) - [Configure Microsoft Defender for Endpoint in Intune](/mem/intune/protect/advanced-threat-protection-configure) |
security | Configure Endpoints Vdi | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/security/defender-endpoint/configure-endpoints-vdi.md | The following configuration settings are recommended: - `%TEMP%*.VHDX` - `%Windir%\TEMP*.VHD` - `%Windir%\TEMP*.VHDX`- - `\\stroageaccount.file.core.windows.net\share**.VHD` - - `\\stroageaccount.file.core.windows.net\share**.VHDX` + - `\\storageaccount.file.core.windows.net\share**.VHD` + - `\\storageaccount.file.core.windows.net\share**.VHDX` #### Real-time Protection |
security | Configure Extension File Exclusions Microsoft Defender Antivirus | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/security/defender-endpoint/configure-extension-file-exclusions-microsoft-defender-antivirus.md | The following table lists and describes the system account environment variables |`%APPDATA%\Microsoft\Internet Explorer\Quick Launch`|`C:\Windows\System32\config\systemprofile\AppData\Roaming\Microsoft\Internet Explorer\Quick Launch`| |`%APPDATA%\Microsoft\Windows\Start Menu`|`C:\Windows\System32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Start Menu`| |`%APPDATA%\Microsoft\Windows\Start Menu\Programs`|`C:\Windows\System32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Start Menu\Programs`|-|`%LOCALAPPDATA%`|`C:\Windows\System32\config\systemprofile\AppData\Local`| +|`%LOCALAPPDATA%`|`C:\Users\USERNAME\AppData\Local`| |`%ProgramData%`|`C:\ProgramData`| |`%ProgramFiles%`|`C:\Program Files`| |`%ProgramFiles%\Common Files`|`C:\Program Files\Common Files`| |
security | Enable Attack Surface Reduction | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/security/defender-endpoint/enable-attack-surface-reduction.md | Example: 6. After the policy is created, select **Close**. +> [!WARNING] +> There is a known issue with the applicability of Attack Surface Reduction on Server OS versions which is marked as compliant without any actual enforcement. Currently, there is no ETA for when this will be fixed. + ### Group Policy > [!WARNING] |
security | Mac Support Kext | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/security/defender-endpoint/mac-support-kext.md | mdatp health ``` ```Output ...-real_time_protection_enabled : false -real_time_protection_available : true +real_time_protection_enabled : true +real_time_protection_available : false ... ``` |
security | Machine | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/security/defender-endpoint/machine.md | search.appverid: met150 |firstSeen|DateTimeOffset|First date and time where the [machine](machine.md) was observed by Microsoft Defender for Endpoint.| |lastSeen|DateTimeOffset|Time and date of the last received full device report. A device typically sends a full report every 24 hours.| |osPlatform|String|Operating system platform.|-|onboardingstatus|String|Status of machine onboarding. Possible values are: "onboarded" and "offboarded".| +|onboardingstatus|String|Status of machine onboarding. Possible values are: "onboarded", "CanBeOnboarded", "Unsupported", and "InsufficientInfo".| |osProcessor|String|Operating system processor. Use osArchitecture property instead.| |version|String|Operating system Version.| |osBuild|Nullable long|Operating system build number.| |
security | Server Migration | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/security/defender-endpoint/server-migration.md | ms.pagetype: security ms.localizationpriority: medium Previously updated : 08/10/2022 Last updated : 09/19/2022 audience: ITPro To facilitate upgrades when Microsoft Endpoint Configuration Manager is not yet 4. Install Microsoft Defender for Endpoint. 5. Apply the onboarding script **for use with Group Policy** downloaded from [Microsoft 365 Defender](https://security.microsoft.com). -To use the script, download it to an installation directory where you have also placed the installation and onboarding packages (see [Configure server endpoints](configure-server-endpoints.md). +To use the script, download it to an installation directory where you have also placed the installation and onboarding packages (see [Configure server endpoints](configure-server-endpoints.md)). EXAMPLE: .\install.ps1 -RemoveMMA <YOUR_WORKSPACE_ID> -OnboardingScript ".\WindowsDefenderATPOnboardingScript.cmd" +For more information on how to use the script, use the PowerShell command "get-help .\install.ps1". + ## Microsoft Endpoint Configuration Manager migration scenarios >[!NOTE] |
security | Microsoft Secure Score Whats New | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/security/defender/microsoft-secure-score-whats-new.md | The more improvement actions you take, the higher your Secure Score will be. For Microsoft Secure Score can be found at <https://security.microsoft.com/securescore> in the [Microsoft 365 Defender portal](microsoft-365-defender-portal.md). +## September 2022 ++New Microsoft Defender for Office 365 recommendations for anti-phishing policies are now available as Secure Score improvement actions: ++- Set the phishing email level threshold at 2 or higher +- Enable impersonated user protection +- Enable impersonated domain protection +- Ensure that mailbox intelligence is enabled +- Ensure that intelligence for impersonation protection is enabled +- Quarantine messages that are detected from impersonated users +- Quarantine messages that are detected from impersonated domains +- Move messages that are detected as impersonated users by mailbox intelligence +- Enable the ΓÇÿshow first contact safety tipΓÇÖ option +- Enable the user impersonation safety tip +- Enable the domain impersonation safety tip +- Enable the user impersonation unusual characters safety tip ++A New SharePoint Online recommendation is now available as a Secure Score improvement action: ++- Sign out inactive users in SharePoint Online + ## August 2022 New Microsoft Information Protection recommendations are now available as Secure Score improvement actions: |
security | Admin Submission | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/security/office-365-security/admin-submission.md | Watch this short video to learn how to use admin submissions in Microsoft Defend - **Select a reason for submitting to Microsoft**: Verify **Should not have been blocked (False positive)** is selected. - - **The email should have been categorized as**: Select **Phish**, **Malware**, or **Spam**. If you're not sure, use your best judgement. + - **The email should have been categorized as**: Select **Phish**, **Malware**, or **Spam**. If you're not sure, use your best judgment. - **Block all emails from this sender or domain**: Select this option to create a block entry for the sender in the Tenant Allow/Block List. For more information about the Tenant Allow/Block List, see [Manage your allows and blocks in the Tenant Allow/Block List](manage-tenant-allow-block-list.md). Watch this short video to learn how to use admin submissions in Microsoft Defend - **File**: Click **Browse files** to find and select the file to submit. - > [!NOTE] - > File submissions are not available in clouds that do not allow for data to leave the environment. **Browse files** is greyed out. - - **Select a reason for submitting to Microsoft**: Verify **Should have been blocked (False negative)** is selected. - - **The email should have been categorized as**: Select **Phish** or **Malware**. If you're not sure, use your best judgement. + - **The email should have been categorized as**: Select **Phish** or **Malware**. If you're not sure, use your best judgment. - **Block this file**: Select this option to create a block entry for the sender in the Tenant Allow/Block List. For more information about the Tenant Allow/Block List, see [Manage your allows and blocks in the Tenant Allow/Block List](manage-tenant-allow-block-list.md). Watch this short video to learn how to use admin submissions in Microsoft Defend - **URL**: Enter the full URL (for example, `https://www.fabrikam.com/marketing.html`), and then select it in the box that appears. - > [!NOTE] - > URL submissions are not available in clouds that do not allow for data to leave the environment. **URL** is greyed out. - - **Select a reason for submitting to Microsoft**: Verify **Should have been blocked (False negative)** is selected. - - **The email should have been categorized as**: Select **Phish** or **Malware**. If you're not sure, use your best judgement. + - **The email should have been categorized as**: Select **Phish** or **Malware**. If you're not sure, use your best judgment. - **Block this URL**: Select this option to create a block entry for the sender in the Tenant Allow/Block List. For more information about the Tenant Allow/Block List, see [Manage your allows and blocks in the Tenant Allow/Block List](manage-tenant-allow-block-list.md). After a few moments, an allow entry will appear on the **URL** tab on the **Tena - **Submitted by** - **Reason for submitting**: The values **Not junk**, **Phish**, **Malware**, and **Spam**. - **Status**: The values **Pending** and **Completed**.- - **Tags**: The default value is **All** or select a [user tag](user-tags.md) from the drop down list. + - **Tags**: The default value is **All** or select a [user tag](user-tags.md) from the drop-down list. When you're finished, click **Apply**. To clear existing filters, click  **Clear filters** in the **Filter** flyout. After a few moments, an allow entry will appear on the **URL** tab on the **Tena - **Submitted by** - **Reason for submitting** - **Status**- - **Tags**: The default value is **All** or select a [user tag](user-tags.md) from the drop down list. + - **Tags**: The default value is **All** or select a [user tag](user-tags.md) from the drop-down list. When you're finished, click **Apply**. :::image type="content" source="../../media/admin-submission-file-filters.png" alt-text="Filter options for email attachment admin submissions."::: - - To group the entries, click  **Group** and select one of the following values from the drop down list: + - To group the entries, click  **Group** and select one of the following values from the drop-down list: - **None** - **Reason** - **Status** After a few moments, an allow entry will appear on the **URL** tab on the **Tena - **Submitted by** - **Reason for submitting** - **Status**- - **Tags**: The default value is **All** or select a [user tag](user-tags.md) from the drop down list. + - **Tags**: The default value is **All** or select a [user tag](user-tags.md) from the drop-down list. When you're finished, click **Apply**. To clear existing filters, click  **Clear filters** in the **Filter** flyout. If you've deployed the [Report Message add-in](enable-the-report-message-add-in. - **Reported from**: The values **Microsoft add-in** or **Third party add-in**. - **Phish simulation**: The values **Yes** or **No**. - **Converted to admin submission**: The values **Yes** or **No**.- - **Tags**: The default value is **All** or select a [user tag](user-tags.md) from the drop down list. + - **Tags**: The default value is **All** or select a [user tag](user-tags.md) from the drop-down list. When you're finished, click **Apply**. To clear existing filters, click  **Clear filters** in the **Filter** flyout. |
security | Defender For Office 365 | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/security/office-365-security/defender-for-office-365.md | Title: Microsoft Defender for Office 365 - - CSH |
security | Detect And Remediate Illicit Consent Grants | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/security/office-365-security/detect-and-remediate-illicit-consent-grants.md | After you have identified an application with illicit permissions, you have seve - You can turn integrated applications off for your tenancy. This is a drastic step that disables the ability for end users to grant consent on a tenant-wide basis. This prevents your users from inadvertently granting access to a malicious application. This isn't strongly recommended as it severely impairs your users' ability to be productive with third party applications. You can do this by following the steps in [Turning Integrated Apps on or off](../../admin/misc/user-consent.md). -## Secure Microsoft 365 like a cybersecurity pro --Your Microsoft 365 subscription comes with a powerful set of security capabilities that you can use to protect your data and your users. Use the [Microsoft 365 security roadmap - Top priorities for the first 30 days, 90 days, and beyond](security-roadmap.md) to implement Microsoft recommended best practices for securing your Microsoft 365 tenant. --- Tasks to accomplish in the first 30 days. These have immediate effect and are low-impact to your users.-- Tasks to accomplish in 90 days. These take a bit more time to plan and implement but greatly improve your security posture.-- Beyond 90 days. These enhancements build in your first 90 days work.- ## See also - [Unexpected application in my applications list](/azure/active-directory/application-access-unexpected-application) walks administrators through various actions they may want to take after realizing there are unexpected applications with access to data. |
security | Detect And Remediate Outlook Rules Forms Attack | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/security/office-365-security/detect-and-remediate-outlook-rules-forms-attack.md | Look for the key EnableUnsafeClientMailRules. If it is there and is set to 1, th Customers with on-premises Exchange installations should consider blocking older versions of Outlook that do not have patches available. Details on this process can be found in the article [Configure Outlook client blocking](/exchange/configure-outlook-client-blocking-exchange-2013-help). -## Secure Microsoft 365 like a cybersecurity pro --Your Microsoft 365 subscription comes with a powerful set of security capabilities that you can use to protect your data and your users. Use the [Microsoft 365 security roadmap - Top priorities for the first 30 days, 90 days, and beyond](security-roadmap.md) to implement Microsoft recommended best practices for securing your Microsoft 365 tenant. --- Tasks to accomplish in the first 30 days. These have immediate effect and are low-impact to your users.--- Tasks to accomplish in 90 days. These take a bit more time to plan and implement but greatly improve your security posture.--- Beyond 90 days. These enhancements build in your first 90 days work.- ## See also: - [Malicious Outlook Rules](https://silentbreaksecurity.com/malicious-outlook-rules/) by SilentBreak Security Post about Rules Vector provides a detailed review of how the Outlook Rules. |
security | Manage Tenant Allow Block List | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/security/office-365-security/manage-tenant-allow-block-list.md | In Microsoft 365 organizations with mailboxes in Exchange Online or standalone E The Tenant Allow/Block List in the Microsoft 365 Defender portal gives you a way to manually override the Microsoft 365 filtering verdicts. The Tenant Allow/Block List is used during mail flow for incoming messages form external senders (does not apply to intra-org messages) and at the time of user clicks. -The Tenant Allow/Block list is available in the the Microsoft 365 Defender portal at <https://security.microsoft.com> \> **Policies & rules** \> **Threat Policies** \> **Tenant Allow/Block Lists** in the **Rules** section. To go directly to the **Tenant Allow/Block Lists** page, use <https://security.microsoft.com/tenantAllowBlockList>. +The Tenant Allow/Block list is available in the Microsoft 365 Defender portal at <https://security.microsoft.com> \> **Policies & rules** \> **Threat Policies** \> **Tenant Allow/Block Lists** in the **Rules** section. To go directly to the **Tenant Allow/Block Lists** page, use <https://security.microsoft.com/tenantAllowBlockList>. For entry creation and configuration instructions, see the following topics: The following list describes what happens in the Tenant Allow/Block List when yo - If the message was blocked by [spoof intelligence](learn-about-spoof-intelligence.md), an allow entry for the sender is created and it appears on the **Spoofed senders** tab in the Tenant Allow Block List. - - If the message was blocked by by [domain or user impersonation protection](set-up-anti-phishing-policies.md#impersonation-settings-in-anti-phishing-policies-in-microsoft-defender-for-office-365) in Defender for Office 365, an allow entry is not created in the Tenant Allow/Block List. Instead, the domain or sender is added to the **Trusted senders and domains section** in the [anti-phishing policy](configure-mdo-anti-phishing-policies.md#use-the-microsoft-365-defender-portal-to-modify-anti-phishing-policies) that detected the message. + - If the message was blocked by [domain or user impersonation protection](set-up-anti-phishing-policies.md#impersonation-settings-in-anti-phishing-policies-in-microsoft-defender-for-office-365) in Defender for Office 365, an allow entry is not created in the Tenant Allow/Block List. Instead, the domain or sender is added to the **Trusted senders and domains section** in the [anti-phishing policy](configure-mdo-anti-phishing-policies.md#use-the-microsoft-365-defender-portal-to-modify-anti-phishing-policies) that detected the message. - If the message was blocked for other reasons, an allow entry for the sender is created and it appears on the **Domains & addresses** tab in the Tenant Allow Block List. - - If the message was not blocked, and allow entry for the sender is not created, so it won't on the **Spoofed senders** tab or the **Domains & addresses** tab. + - If the message was not blocked, and allow entry for the sender is not created, it won't on the **Spoofed senders** tab or the **Domains & addresses** tab. By default, allow entries for **domains and email addresses**, **files** and **URLs** expire after 30 days, which is also the maximum. Allow entries for **spoofed senders** never expire. By default, allow entries for **domains and email addresses**, **files** and **U ## What to expect after you add an allow or block entry -After you add an allow entry through the Submissions portal or a block entry in the Tenant Allow/Block List, the entry should start working immediately. +After you add an allow entry through the Submissions portal or a block entry in the Tenant Allow/Block List, the entry should start working immediately 99.999% of the time. For the rest, it could take up to 24 hours. We recommend letting entries automatically expire after 30 days to see if the system has learned about the allow or block. If not, you should make another entry to give the system another 30 days to learn. |
security | Microsoft 365 Policies Configurations | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/security/office-365-security/microsoft-365-policies-configurations.md | Watch this video for a quick overview of identity and device access configuratio ## Intended audience -These recommendations are intended for enterprise architects and IT professionals who are familiar with Microsoft 365 cloud productivity and security services, which includes Azure AD (identity), Microsoft Intune (device management), and Microsoft Purview Information Protection (data protection). +These recommendations are intended for enterprise architects and IT professionals who are familiar with Microsoft 365 cloud productivity and security services, which include Azure AD (identity), Microsoft Intune (device management), and Microsoft Purview Information Protection (data protection). ### Customer environment This guidance shows you how to implement a set of policies to protect access to - [Configure your tenant for increased security](tenant-wide-setup-for-increased-security.md) - Recommendations that apply to starting point security for your tenant. --- [Security roadmap: Top priorities for the first 30 days, 90 days, and beyond](security-roadmap.md)-- Recommendations that include logging, data governance, admin access, and threat protection. - ### Windows 11 or Windows 10 with Microsoft 365 Apps for enterprise Windows 11 or Windows 10 with Microsoft 365 Apps for enterprise is the recommended client environment for PCs. We recommend Windows 11 or Windows 10 because Azure is designed to provide the smoothest experience possible for both on-premises and Azure AD. Windows 11 or Windows 10 also includes advanced security capabilities that can be managed through Intune. Microsoft 365 Apps for enterprise includes the latest versions of Office applications. These use modern authentication, which is more secure and a requirement for Conditional Access. These apps also include enhanced compliance and security tools. |
security | Office 365 Ti | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/security/office-365-security/office-365-ti.md | Title: Threat investigation & response capabilities - Microsoft Defender for Office 365 Plan 2 + Title: Threat investigation & response capabilities in Microsoft Defender for Office 365 f1.keywords: - NOCSH Use the Incidents list (this is also called Investigations) to see a list of in To view the list of current incidents for your organization in the Microsoft 365 Defender portal at <https://security.microsoft.com>, go to **Incidents & alerts** \> **Incidents**. Or, to go directly to the **Incidents** page, use <https://security.microsoft.com/incidents>. ### Attack simulation training Microsoft Defender for Office 365 uses role-based access control. Permissions ar |Activity|Roles and permissions| |||-|Use the Microsoft Defender Vulnerability Management dashboard (or the new [Security dashboard](security-dashboard.md) <p> View information about recent or current threats|One of the following: <ul><li>**Global Administrator**</li><li>**Security Administrator**</li><li>**Security Reader**</li></ul> <p> These roles can be assigned in either Azure Active Directory (<https://portal.azure.com>) or the Microsoft 365 admin center (<https://admin.microsoft.com>).| +|Use the Microsoft Defender Vulnerability Management dashboard <p> View information about recent or current threats|One of the following: <ul><li>**Global Administrator**</li><li>**Security Administrator**</li><li>**Security Reader**</li></ul> <p> These roles can be assigned in either Azure Active Directory (<https://portal.azure.com>) or the Microsoft 365 admin center (<https://admin.microsoft.com>).| |Use [Explorer (and real-time detections)](threat-explorer.md) to analyze threats|One of the following: <ul><li>**Global Administrator**</li><li>**Security Administrator**</li><li>**Security Reader**</li></ul> <p> These roles can be assigned in either Azure Active Directory (<https://portal.azure.com>) or the Microsoft 365 admin center (<https://admin.microsoft.com>).| |View Incidents (also referred to as Investigations) <p> Add email messages to an incident|One of the following: <ul><li>**Global Administrator**</li><li>**Security Administrator**</li><li>**Security Reader**</li></ul> <p> These roles can be assigned in either Azure Active Directory (<https://portal.azure.com>) or the Microsoft 365 admin center (<https://admin.microsoft.com>).| |Trigger email actions in an incident <p> Find and delete suspicious email messages|One of the following: <ul><li>**Global Administrator**</li><li>**Security Administrator** plus the **Search and Purge** role</li></ul> <p> The **Global Administrator** and **Security Administrator** roles can be assigned in either Azure Active Directory (<https://portal.azure.com>) or the Microsoft 365 admin center (<https://admin.microsoft.com>). <p> The **Search and Purge** role must be assigned in the **Email & collaboration roles** in the Microsoft 36 Defender portal (<https://security.microsoft.com>).| |
security | Office365 Security Incident Response Overview | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/security/office-365-security/office365-security-incident-response-overview.md | - Title: Security Incident Response - - NOCSH --- Previously updated : 04/27/2018--- - o365_security_incident_response - - M365-security-compliance -- - MET150 -description: This solution tells you what the most common cybersecurity attacks might look like in Microsoft 365 and how to respond to them -- - seo-marvel-apr2020 -----# Security Incident Response --**Applies to** -- [Exchange Online Protection](exchange-online-protection-overview.md)-- [Microsoft Defender for Office 365 plan 1 and plan 2](defender-for-office-365.md)-- [Microsoft 365 Defender](../defender/microsoft-365-defender.md)-- **Summary:** This solution tells you what the indicators are for the most common cybersecurity attacks in Office 365, how to positively confirm any given attack, and how to respond to it. --## Learn how to respond to cyberattacks --Not all cyberattacks can be thwarted. Attackers are constantly looking for new weaknesses in your defensive strategy or they are exploiting old ones. Knowing how to recognize an attack allows you to respond to it faster, which shortens the duration of the security incident. --This series of article helps you understand what a particular type of attack might look like in Microsoft 365 and gives you steps you can take to respond. They are quick entry points to understanding: --- What the attack is and how it works.--- What signs, called indicators of compromise (IOC), to look for and how to look for them.--- How to positively confirm the attack.--- Steps to take to cut off the attack and better protect your organization in the future.--- Links to in-depth information on each attack type.--Check back here monthly as more articles will be added over time. --## Detect and remediate articles --- [Detect and Remediate Illicit Consent Grants in Office 365](detect-and-remediate-illicit-consent-grants.md)--- [Detect and Remediate Outlook Rules and Custom Forms Injections Attacks in Office 365](detect-and-remediate-outlook-rules-forms-attack.md)--## Incident response articles --- [Responding to a Compromised Email Account in Office 365](responding-to-a-compromised-email-account.md)--## Secure Microsoft 365 like a cybersecurity pro --Your Microsoft 365 subscription comes with a powerful set of security capabilities that you can use to protect your data and your users. Use the [Microsoft 365 security roadmap - Top priorities for the first 30 days, 90 days, and beyond](security-roadmap.md) to implement Microsoft recommended best practices for securing your Microsoft 365 organization. --- Tasks to accomplish in the first 30 days. These have immediate affect and are low-impact to your users.--- Tasks to accomplish in 90 days. These take a bit more time to plan and implement but greatly improve your security posture--- Beyond 90 days. These enhancements build in your first 90 days work. |
security | Old Index | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/security/office-365-security/old-index.md | - Title: Office 365 Security overview, Microsoft Defender for Office 365, EOP, MSDO--- Previously updated : 08/13/2020-- - - MET150 - - MOE150 -- - M365-security-compliance - - m365initiative-defender-office365 -description: Security in Office 365, from EOP to Defender for Office 365 Plans 1 and 2, Standard vs. Strict security configurations, and more. Understand what you have and learn how to secure your properties. -----# Office 365 security --**Applies to** -- [Exchange Online Protection](exchange-online-protection-overview.md)-- [Microsoft Defender for Office 365 plan 1 and plan 2](defender-for-office-365.md)--This article will introduce you to your new security properties in the Cloud. Whether you're part of a Security Operations Center, you're a Security Administrator new to the space, or you want a refresher, let's get started. --> [!CAUTION] -> If you're using **Outlook.com**, **Microsoft 365 Family**, or **Microsoft 365 Personal**, and need *Safe Links* or *Safe Attachments* info, ***click this link***: [Advanced Outlook.com security for Microsoft 365 subscribers](https://support.microsoft.com/office/advanced-outlook-com-security-for-office-365-subscribers-882d2243-eab9-4545-a58a-b36fee4a46e2). --## Office 365 security spelled out --Every Office 365 subscription comes with security capabilities. The goals and actions that you can take depend on the focus of these different subscriptions. In Office 365 security, there are three main security services (or products) tied to your subscription type: --1. Exchange Online Protection (EOP) -1. Microsoft Defender for Office 365 Plan 1 (Defender for Office P1) -1. Microsoft Defender for Office 365 Plan 2 (Defender for Office P2) --> [!NOTE] -> If you bought your subscription and need to roll out security features *right now*, skip to the steps in the [Protect Against Threats](protect-against-threats.md) article. If you're new to your subscription and would like to know your license before you begin, browse Billing > Your Products in the [Microsoft 365 admin center](https://admin.microsoft.com/AdminPortal/#/homepage). --Office 365 security builds on the core protections offered by EOP. EOP is present in any subscription where Exchange Online mailboxes can be found (remember, all the security products discussed here are Cloud-based). --You may be accustomed to seeing these three components discussed in this way: --|EOP|Microsoft Defender for Office 365 P1|Microsoft Defender for Office 365 P2| -|||| -|Prevents broad, volume-based, known attacks.|Protects email and collaboration from zero-day malware, phish, and business email compromise.|Adds post-breach investigation, hunting, and response, as well as automation, and simulation (for training).| --But in terms of architecture, let's start by thinking of each piece as cumulative layers of security, each with a security emphasis. More like this: --<!--:::image type="content" source="../../media/tp-EOPATPStack.PNG" alt-text="Placeholder graphic.":::--> ---Though each of these services emphasizes a goal from among Protect, Detect, Investigate, and Respond, ***all*** the services can carry out ***any*** of the goals of protecting, detecting, investigating, and responding. --The core of Office 365 security is EOP protection. Microsoft Defender for Office 365 P1 contains EOP in it. Defender for Office 365 P2 contains P1 and EOP. The structure is cumulative. That's why, when configuring this product, you should start with EOP and work to Defender for Office 365. --Though email authentication configuration takes place in public DNS, it's important to configure this feature to help defend against spoofing. *If you have EOP,* ***you should [configure email authentication](email-validation-and-authentication.md)***. --If you have an Office 365 E3, or below, you have EOP, but with the option to buy standalone Defender for Office 365 P1 through upgrade. If you have Office 365 E5, you already have Defender for Office 365 P2. --> [!TIP] -> If your subscription is neither Office 365 E3 or E5, you can still check to see if you have the option to upgrade to Microsoft Defender for Office 365 P1. If you're interested, [this webpage](https://www.microsoft.com/microsoft-365/exchange/advance-threat-protection#coreui-contentrichblock-x07wids) lists subscriptions eligible for the Microsoft Defender for Office 365 P1 upgrade (check the end of the page for the fine-print). --## The Office 365 security ladder from EOP to Microsoft Defender for Office 365 -- --> [!IMPORTANT] -> Learn the details on these pages: [Exchange Online Protection](exchange-online-protection-overview.md), and [Defender for Office 365](defender-for-office-365.md). --What makes adding Microsoft Defender for Office 365 plans an advantage to pure EOP threat management can be difficult to tell at first glance. To help sort out if an upgrade path is right for your organization, let's look at the capabilities of each product when it comes to: --- preventing and detecting threats-- investigating-- responding--starting with **Exchange Online Protection**: -<p> --|Prevent/Detect|Investigate|Respond| -|||| -|Technologies include:<ul><li>spam</li><li>phish</li><li>malware</li><li>bulk mail</li><li>spoof intelligence</li><li>impersonation detection</li><li>Admin Quarantine</li><li>Admin and user submissions of False Positives and False Negatives</li><li>Allow/Block for URLs and Files</li><li>Reports</li></ul>|<li>Audit log search</li><li>Message Trace</li>|<li>Zero-hour auto purge (ZAP)</li><li>Refinement and testing of Allow and Block lists</li>| --If you want to dig in to EOP, **[jump to this article](exchange-online-protection-overview.md)**. --Because these products are cumulative, if you evaluate Microsoft Defender for Office 365 P1 and decide to subscribe to it, you'll add these abilities. --Gains with **Defender for Office 365, Plan 1** (to date): -<p> --|Prevent/Detect|Investigate|Respond| -|||| -|Technologies include everything in EOP plus:<ul><li>Safe attachments</li><li>Safe links<li>Microsoft Defender for Office 365 protection for workloads (ex. SharePoint Online, Teams, OneDrive for Business)</li><li>Time-of-click protection in email, Office clients, and Teams</li><li>anti-phishing in Defender for Office 365</li><li>User and domain impersonation protection</li><li>Alerts, and SIEM integration API for alerts</li>|<li>SIEM integration API for detections</li><li>**Real-time detections tool**</li><li>URL trace</li>|<li>Same</li></ul> --So, Microsoft Defender for Office 365 P1 expands on the ***prevention*** side of the house, and adds extra forms of ***detection***. --Microsoft Defender for Office 365 P1 also adds **Real-time detections** for investigations. This threat hunting tool's name is in bold because having it is clear means of *knowing* you have Defender for Office 365 P1. It doesn't appear in Defender for Office 365 P2. --Gains with **Defender for Office 365, Plan 2** (to date): -<p> --|Prevent/Detect|Investigate|Respond| -|||| -|Technologies include everything in EOP, and Microsoft Defender for Office 365 P1 plus:<ul><li>Same</li>|<li>**Threat Explorer**</li><li>Threat Trackers</li><li>Campaign views</li>|<li>Automated Investigation and Response (AIR)</li><li>AIR from Threat Explorer</li><li>AIR for compromised users</li><li>SIEM Integration API for Automated Investigations</li> --So, Microsoft Defender for Office 365 P2 expands on the ***investigation and response*** side of the house, and adds a new hunting strength. Automation. --In Microsoft Defender for Office 365 P2, the primary hunting tool is called **Threat Explorer** rather than Real-time detections. If you see Threat Explorer when you navigate to the Defender for Cloud, you're in Microsoft Defender for Office 365 P2. --To get into the details of Microsoft Defender for Office 365 P1 and P2, **[jump to this article](defender-for-office-365.md)**. --> [!TIP] -> EOP and Microsoft Defender for Office 365 are also different when it comes to end-users. In EOP and Defender for Office 365 P1, the focus is *awareness*, and so those two services include the *Report message Outlook add-in* so users can report emails they find suspicious, for further analysis. <p> In Defender for Office 365 P2 (which contains everything in EOP and P1), the focus shifts to *further training* for end-users, and so the Security Operations Center has access to a powerful *Threat Simulator* tool, and the end-user metrics it provides. --## Microsoft Defender for Office 365 Plan 1 vs. Plan 2 cheat sheet --This quick-reference will help you understand what capabilities come with each Microsoft Defender for Office 365 subscription. When combined with your knowledge of EOP features, it can help business decision makers determine what Microsoft Defender for Office 365 is best for their needs. --|Defender for Office 365 Plan 1|Defender for Office 365 Plan 2| -||| -|Configuration, protection, and detection capabilities: <ul><li>[Safe Attachments](safe-attachments.md)</li><li>[Safe Links](safe-links.md)</li><li>[Safe Attachments for SharePoint, OneDrive, and Microsoft Teams](mdo-for-spo-odb-and-teams.md)</li><li>[Anti-phishing protection in Defender for Office 365](set-up-anti-phishing-policies.md#exclusive-settings-in-anti-phishing-policies-in-microsoft-defender-for-office-365)</li><li>[Real-time detections](threat-explorer.md)</li></ul>|Defender for Office 365 Plan 1 capabilities <p> plus <p> Automation, investigation, remediation, and education capabilities: <ul><li>[Threat Trackers](threat-trackers.md)</li><li>[Threat Explorer](threat-explorer.md)</li><li>[Automated investigation and response](office-365-air.md)</li><li>[Attack Simulator](attack-simulator.md)</li></ul>| --- Microsoft Defender for Office 365 Plan 2 is included in Office 365 E5, Office 365 A5, and Microsoft 365 E5.--- Microsoft Defender for Office 365 Plan 1 is included in Microsoft 365 Business Premium.--- Microsoft Defender for Office 365 Plan 1 and Defender for Office 365 Plan 2 are each available as an add-on for certain subscriptions. To learn more, here's another link [Feature availability across Microsoft Defender for Office 365 plans](/office365/servicedescriptions/office-365-advanced-threat-protection-service-description#feature-availability-across-advanced-threat-protection-atp-plans).--- The [Safe Documents](safe-docs.md) feature is only available to users with the Microsoft 365 E5 or Microsoft 365 E5 Security licenses (not included in Microsoft Defender for Office 365 plans).--- If your current subscription doesn't include Microsoft Defender for Office 365 and you want it, [contact sales to start a trial](https://info.microsoft.com/ww-landing-M365SMB-web-contact.html), and find out how Microsoft Defender for Office 365 can work for in your organization.--> [!TIP] -> ***Insider tip***. You can use the Microsoft Docs table of contents to learn about EOP and Microsoft Defender for Office 365. Navigate back to this page, [Office 365 Security overview](index.yml), and you'll notice that table of contents organization in the side-bar. It begins with Deployment (including migration) and then continues into prevention, detection, investigation, and response. <p> This structure is divided so that **Security Administration** topics are followed by **Security Operations** topics. If you're a new member of either job role, use the link in this tip, and your knowledge of the table of contents, to help learn the space. Remember to use *feedback links* and *rate articles* as you go. Feedback helps us improve what we offer you. --## Where to go next --If you're a Security Admin, you may need to configure DKIM or DMARC for your mail. You may want to roll out 'Strict' security presets for your priority users, or look for what's new in the product. Or if you're with Security Ops, you may want to leverage Real-time detections or Threat Explorer to investigate and respond, or train end-user detection with Attack Simulator. Either way, here are some additional recommendations for what to look at next. --[Email Authentication, including SPF, DKIM, and DMARC (with links to setup of all three)](email-validation-and-authentication.md) --[See the specific recommended 'golden' configs](recommended-settings-for-eop-and-office365.md) and [use their recommended presets to configure security policies quickly](preset-security-policies.md) --Catch up on [what's new in Microsoft Defender for Office 365 (including EOP developments)](whats-new-in-defender-for-office-365.md) --[Use Threat Explorer or Real-time detections](threat-explorer.md) --Use [Attack Simulator in Microsoft Defender for Office 365](attack-simulator.md) |
security | Reporting And Message Trace In Exchange Online Protection | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/security/office-365-security/reporting-and-message-trace-in-exchange-online-protection.md | - Title: Reporting and message trace - - NOCSH --- Previously updated : ---- - seo-marvel-apr2020 -description: In this article, you'll learn about reports and troubleshooting tools available to Microsoft Exchange Online Protection (EOP) admins. -----# Reporting and message trace in EOP ---**Applies to** -- [Exchange Online Protection](exchange-online-protection-overview.md)-- [Microsoft Defender for Office 365 plan 1 and plan 2](defender-for-office-365.md)-- [Microsoft 365 Defender](../defender/microsoft-365-defender.md)--In Microsoft 365 organizations with mailboxes in Exchange Online or standalone Exchange Online Protection (EOP) organizations without Exchange Online mailboxes, EOP offers many different reports that can help you determine the overall status and health of your organization. There are also tools to help you troubleshoot specific events (such as a message not arriving to its intended recipients), and auditing reports to aid with compliance requirements. --## Usage reports --- **Microsoft 365 groups activity**: View information about the number of Microsoft 365 groups that are created and used. For more information, see [Microsoft 365 Reports in the admin center - Microsoft 365 groups](../../admin/activity-reports/office-365-groups.md).-- **Email activity**: View information about the number of messages sent, received, and read in your whole organization, and by specific users. For more information, see [Microsoft 365 Reports in the admin center - Email activity](../../admin/activity-reports/email-activity.md).-- **Email app usage**: View information about the email apps that are used. This includes the total number of connections for each app, and the versions of Outlook that are connecting. For more information, see [Microsoft 365 Reports in the admin center - Email apps usage](../../admin/activity-reports/email-apps-usage.md).-- **Mailbox usage**: View information about storage used, quota consumption, item count, and last activity (send or read activity) for mailboxes. For more information, see [Microsoft 365 Reports in the admin center - Mailbox usage](../../admin/activity-reports/mailbox-usage.md).--## Security reports in the Microsoft 365 defender portal --These enhanced reports provide an interactive reporting experience for EOP admins, which includes summary information, and the ability to drill down for more details. --- **Defender for Office 365**: View information about Safe Links and Safe Attachments that are part of Microsoft Defender for Office 365. For more information, see [View Defender for Office 365 reports in the Microsoft 365 Defender portal](view-reports-for-mdo.md).-- **EOP**: View information about malware detections, spoofed mail, spam detections, and mail flow to and from your organization. For more information, see [View email security reports in the Microsoft 365 Defender portal](view-email-security-reports.md).--## Mail flow insights in the Security & Compliance Center --For more information, see [Mail flow insights in the Security & Compliance Center](mail-flow-insights-v2.md). --## Custom reports using Microsoft Graph --Programmatically create reports that are available in the admin center by using Microsoft Graph. For more information, see [Overview of Microsoft Graph](/graph/overview) and [Working with Office 365 usage reports in Microsoft Graph](/graph/api/resources/report). --## Message trace --Follows email messages as they travel through EOP. You can determine if an email message was received, rejected, deferred, or delivered by the service. It also shows what actions were taken on the message before it reached its final status. --You can use this information to efficiently answer your user's questions, troubleshoot mail flow issues, validate policy changes, and alleviates the need to contact technical support for assistance. --See [Message trace in the Microsoft 365 Defender portal](message-trace-scc.md). --## Audit logging --Tracks specific changes made by admins to your organization. These reports can help you troubleshoot configuration issues or find the cause of security or compliance-related problems. See [Auditing reports in Exchange Online](/exchange/security-and-compliance/exchange-auditing-reports/exchange-auditing-reports). --## Reporting and message trace data availability and latency --The following table describes when EOP reporting and message trace data is available and for how long. --|Report type|Data available for (look back period)|Latency| -|||| -|Mail protection summary reports|90 days|Message data aggregation is mostly complete within 24-48 hours. Some minor incremental aggregated changes may occur for up to 5 days.| -|Mail protection detail reports|90 days|For detail data that's less than 7 days old, data should appear within 24 hours but may not be complete until 48 hours. Some minor incremental changes may occur for up to 5 days. <p> To view detail reports for messages that are greater than 7 days old, results may take up to a few hours.| -|Message trace data|90 days|When you run a message trace for messages that are less than 7 days old, the messages should appear within 5-30 minutes.<p> When you run a message trace for messages that are greater than 7 days old, results may take up to a few hours.| --> [!NOTE] -> Data availability and latency is the same whether requested via the admin center or remote PowerShell. |
security | Reports And Insights In Security And Compliance | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/security/office-365-security/reports-and-insights-in-security-and-compliance.md | - Title: Smart reports and insights - - NOCSH --- Previously updated : -- - MET150 - - MOE150 -- - M365-security-compliance -description: Learn about the smart reports and insights, and how to use them to view and explore data and take quick actions. ------# Smart reports and insights in the Security & Compliance Center --**Applies to** -- [Exchange Online Protection](exchange-online-protection-overview.md)-- [Microsoft Defender for Office 365 plan 1 and plan 2](defender-for-office-365.md)-- [Microsoft 365 Defender](../defender/microsoft-365-defender.md)--Security teams can use the smart reports and insights in the Security & Compliance Center to monitor the health and security of their organizations. This information is presented in the **Dashboard** at <https://protection.office.com/insightdashboard>: ---The smart reports and insights on the **Dashboard** have the following capabilities: --- Highlight problem areas.-- Recommendations and links to view and explore data.-- Take quick action.--For example, if users in your organization are suddenly reporting a high number of email messages as spam, you should verify the settings in your anti-spam policies. --## Types of reports in the Security & Compliance Center --The following table list the reports that are available in the **Dashboard**: --|Type of information|How to get there|Where to go to learn more| -|||| -|**All up** <p> Top insights and recommendations, and links to available security reports and compliance reports.|<https://protection.office.com/insightdashboard>|[Reports in the Security & Compliance Center](../../compliance/reports-in-security-and-compliance.md)| -|**Email & collaboration reports** <p> Threat detections, malware trends, top targeted users, details about sent and received email messages, and more.|<https://security.microsoft.com/emailandcollabreport>|[View email security reports](view-email-security-reports.md) <p> [View reports for Defender for Office 365](view-reports-for-mdo.md)| -|**Explorer** (also referred to as Threat explorer) or **Real-time detections** <p> Suspected malware detected in email and files in Microsoft 365.|<https://security.microsoft.com/threatexplorer> <p> <https://security.microsoft.com/realtimereports>|[Threat Explorer (or real-time detections)](threat-explorer.md)| --## Related topics --[Microsoft 365 Defender portal](../defender/microsoft-365-defender-portal.md) --[Protect against threats in Office 365](protect-against-threats.md) |
security | Responding To A Compromised Email Account | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/security/office-365-security/responding-to-a-compromised-email-account.md | To unblock a mailbox from sending mail, follow the procedures in [Removing a use 3. Make sure that your contact information, such as telephone numbers and addresses, is correct. -## Secure Microsoft 365 like a cybersecurity pro --Your Microsoft 365 subscription comes with a powerful set of security capabilities that you can use to protect your data and your users. Use the [Microsoft 365 security roadmap - Top priorities for the first 30 days, 90 days, and beyond](security-roadmap.md) to implement Microsoft recommended best practices for securing your Microsoft 365 tenant. --- Tasks to accomplish in the first 30 days. These have immediate affect and are low-impact to your users.-- Tasks to accomplish in 90 days. These take a bit more time to plan and implement but greatly improve your security posture.-- Beyond 90 days. These enhancements build in your first 90 days work.- ## See also - [Detect and Remediate Outlook Rules and Custom Forms Injections Attacks in Microsoft 365](detect-and-remediate-outlook-rules-forms-attack.md) |
security | Security Dashboard | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/security/office-365-security/security-dashboard.md | - Title: Security dashboard overview - - NOCSH ----- - MET150 - - MOE150 -- - M365-security-compliance -- - seo-marvel-apr2020 -description: Use the new Security Dashboard to review Office 365 Threat Protection Status, and view and act on security alerts. -----# Security dashboard in the Security & Compliance Center ---## Basic functions and how to open Security dashboard --The Security & Compliance Center at <https://protection.office.com> enables your organization to manage data protection and compliance. Assuming you have the necessary permissions, the Security Dashboard enables you to review your Threat Protection Status, as well as view and act on security alerts. --Watch the video to get an overview, and then read this article to learn more. --> [!VIDEO https://www.microsoft.com/videoplayer/embed/RE1VV3o] --Depending on what your organization's subscription includes, the Security Dashboard includes several widgets, such as Threat Management Summary, Threat Protection Status, Global Weekly Threat Detections, Malware, and more, as described in the following sections. --To view the Security Dashboard in the Security & Compliance Center, go to go to **Threat management** \> **Dashboard**. To go directly to the Security dashboard, use <https://protection.office.com/searchandinvestigation/dashboard>. --> [!NOTE] -> You must be a global administrator, a security administrator, or a security reader to view the Security Dashboard. Some widgets require additional permissions to view. To learn more, see [Permissions in the Security & Compliance Center](permissions-in-the-security-and-compliance-center.md)[. --## Threat Management Summary --The Threat Management Summary widget tells you at a glance how your organization was protected from threats over the past seven (7) days. ---The information you'll see in the Threat Management Summary depends on what your subscription includes. The following table describes what information is included for Office 365 E3 and Office 365 E5. --|Office 365 E3|Office 365 E5| -||| -|Malware messages blocked<br>Phishing messages blocked<br>Messages reported by users<br><br><br><br>|Malware messages blocked<br>Phishing messages blocked<br>Messages reported by users<br>Zero-day malware blocked<br>Advanced phishing messages detected<br>Malicious URLs blocked| --To view or access the Threat Management Summary widget, you must have permissions to view Defender for Office 365 reports. To learn more, see [What permissions are needed to view the Defender for Office 365 reports?](view-reports-for-mdo.md#what-permissions-are-needed-to-view-the-defender-for-office-365-reports). --## Threat Protection Status --The Threat Protection Status widget shows threat protection effectiveness with a trending and detailed view of phish and malware. ---The details depend on whether your Microsoft 365 subscription includes [Exchange Online Protection](exchange-online-protection-overview.md) (EOP) with or without [Microsoft Defender for Office 365](defender-for-office-365.md). --|If your subscription includes...|You'll see these details| -||| -|EOP but not Microsoft Defender for Office 365|Malicious email that was detected and blocked by EOP.<p> See [Threat Protection Status report (EOP)](view-email-security-reports.md#threat-protection-status-report).| -|Microsoft Defender for Office 365|Malicious content and malicious email detected and blocked by EOP and Defender for Office 365 <p> Aggregated count of unique email messages with malicious content blocked by the anti-malware engine, [zero-hour auto purge](zero-hour-auto-purge.md), and Defender for Office 365 features (including [Safe Links](safe-links.md), [Safe Attachments](safe-attachments.md), and [Anti-phishing in Defender for Office 365](set-up-anti-phishing-policies.md#exclusive-settings-in-anti-phishing-policies-in-microsoft-defender-for-office-365)). <p> See [Threat protection status report](view-reports-for-mdo.md#threat-protection-status-report).| --To view or access the Threat Protection Status widget, you must have permissions to view Defender for Office 365 reports. To learn more, see [What permissions are needed to view the Defender for Office 365 reports?](view-reports-for-mdo.md#what-permissions-are-needed-to-view-the-defender-for-office-365-reports) --## Global Weekly Threat Detections --The Global Weekly Threat Detections widget shows how many threats were detected in email messages over the past seven (7) days. ---The metrics are calculated as described in the following table: --|Metric|How it's calculated| -||| -|Messages scanned|Number of email messages scanned multiplied by the number of recipients| -|Threats stopped|Number of email messages identified as containing malware multiplied by the number of recipients| -|Blocked by [Defender for Office 365](defender-for-office-365.md)|Number of email messages blocked by Defender for Office 365 multiplied by the number of recipients| -|Removed after delivery|Number of messages removed by [zero-hour auto purge (ZAP)](zero-hour-auto-purge.md) multiplied by the number of recipients| --## Malware --Malware widgets show details about malware trends and malware family types over the past seven (7) days. ---## Insights --Insights not only surface key issues you should review, they also include recommendations and actions to consider. ---For example, you might see that phishing email messages are being delivered because some users have disabled their junk mail options. To learn more about how insights work, see [Reports and insights in the Security & Compliance Center](reports-and-insights-in-security-and-compliance.md). --## Threat investigation and response --If your organization's subscription includes [Microsoft Defender for Office 365 Plan 2](office-365-ti.md), your Security Dashboard has a section that includes advanced threat investigation and response tools. These tools include [automated investigation and response capabilities](automated-investigation-response-office.md). Automated investigation and response can be helpful in scenarios such as [addressing compromised user accounts quickly](address-compromised-users-quickly.md). --To learn more, see [Get started using Automated investigation and response (AIR) in Office 365](office-365-air.md). --## Trends --Near the bottom of the Security Dashboard is a **Trends** section, which summarizes email flow trends for your organization. Reports provide information about email categorized as spam, malware, phishing attempts, and good email. Click a tile to view more detailed information in the report. ---And, if your organization's subscription includes [Defender for Office 365 Plan 2](office-365-ti.md), you will also have a **Recent threat management alerts** report in this section that enables your security team to view and take action on high-priority security alerts. --To view or access the Sent and Received Email widget, you must have permissions to view Defender for Office 365 reports. To learn more, see [What permissions are needed to view the Defender for Office 365 reports?](view-reports-for-mdo.md#what-permissions-are-needed-to-view-the-defender-for-office-365-reports). --To view or access the Recent Threat Management Alerts widget, you must have permissions to view alerts. To learn more, see [RBAC permissions required to view alerts](../../compliance/alert-policies.md#rbac-permissions-required-to-view-alerts). --## Related articles --[View email security reports in the Security & Compliance Center](view-email-security-reports.md) --[View reports for Microsoft Defender for Office 365](view-reports-for-mdo.md) --[Defender for Office 365](defender-for-office-365.md) --[Office 365 Threat investigation and response](office-365-ti.md) |
security | Security Roadmap | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/security/office-365-security/security-roadmap.md | - Title: Microsoft 365 security roadmap - Top priorities - - NOCSH --- Previously updated : 08/20/2021--- - Ent_O365 - - Strat_O365_IP - - M365-security-compliance - - MET150 -description: Top recommendations from Microsoft's cybersecurity team for implementing security capabilities to protect your Microsoft 365 environment. -----# Security roadmap - Top priorities for the first 30 days, 90 days, and beyond ---This article includes top recommendations from Microsoft's cybersecurity team for implementing security capabilities to protect your Microsoft 365 environment. This article is adapted from a Microsoft Ignite session ΓÇö [Secure Microsoft 365 like a cybersecurity pro: Top priorities for the first 30 days, 90 days, and beyond](https://www.youtube.com/watch?v=luignzNyR-o). This session was developed and presented by Mark Simos and Matt Kemelhar, Enterprise Cybersecurity Architects. --In this article: --- [Roadmap outcomes](security-roadmap.md#Roadmap)-- [30 days ΓÇö powerful quick wins](security-roadmap.md#Thirdaydays)-- [90 days ΓÇö enhanced protections](security-roadmap.md#Ninetydays)-- [Beyond](security-roadmap.md#Beyond)--## Roadmap outcomes -<a name="Roadmap"> </a> --These roadmap recommendations are staged across three phases in a logical order with the following goals. --|Time frame|Outcomes| -||| -|30 days|Rapid configuration: <ul><li>Basic admin protections.</li><li>Logging and analytics.</li><li>Basic identity protections.</li></ul> <p> Tenant configuration. <p> Prepare stakeholders.| -|90 days|Advanced protections: <ul><li>Admin accounts.</li><li>Data and user accounts.</li></ul> <p> Visibility into compliance, threat, and user needs. <p> Adapt and implement default policies and protections.| -|Beyond|Adjust and refine key policies and controls. <p> Extend protections to on-premises dependencies. <p> Integrate with business and security processes (legal, insider threat, etc.).| --## 30 days ΓÇö powerful quick wins -<a name="Thirdaydays"> </a> --These tasks can be accomplished quickly and have low impact to users. --|Area|Tasks| -||| -|Security management|<ul><li>Check Secure Score and take note of your current score (<https://security.microsoft.com/securescore>).</li><li>Turn on audit logging for Office 365. See [Search the audit log](../../compliance/search-the-audit-log-in-security-and-compliance.md).</li><li>[Configure Microsoft 365 for increased security](tenant-wide-setup-for-increased-security.md).</li><li>Regularly review dashboards and reports in the Microsoft 365 Defender portal and Defender for Cloud Apps.</li></ul>| -|Threat protection|[Connect Microsoft 365 to Microsoft Defender for Cloud Apps](/cloud-app-security/connect-office-365-to-microsoft-cloud-app-security) to start monitoring using the default threat detection policies for anomalous behaviors. It takes seven days to build a baseline for anomaly detection. <p> Implement protection for admin accounts:<ul><li>Use dedicated admin accounts for admin activity.</li><li>Enforce multi-factor authentication (MFA) for admin accounts.</li><li>Use a [highly secure Windows device](/windows-hardware/design/device-experiences/oem-highly-secure) for admin activity.</li></ul>| -|Identity and access management|<ul><li>[Enable Azure Active Directory Identity Protection](/azure/active-directory/active-directory-identityprotection-enable).</li><li>For federated identity environments, enforce account security (password length, age, complexity, etc.).</li></ul>| -|Information protection|Review example information protection recommendations. Information protection requires coordination across your organization. Get started with these resources:<ul><li>[Office 365 Information Protection for GDPR](/compliance/regulatory/gdpr)</li><li>[Configure Teams with three tiers of protection](../../solutions/configure-teams-three-tiers-protection.md) (includes sharing, classification, Microsoft Purview data loss prevention, and Azure Information Protection)</li></ul>| --## 90 days ΓÇö enhanced protections -<a name="Ninetydays"> </a> --These tasks take a bit more time to plan and implement but greatly increase your security posture. --|Area|Task| -||| -|Security management|<ul><li>Check Secure Score for recommended actions for your environment (<https://security.microsoft.com/securescore>).</li><li>Continue to regularly review dashboards and reports in the Microsoft 365 Defender portal, Defender for Cloud Apps, and SIEM tools.</li><li>Look for and implement software updates.</li><li>Conduct attack simulations for spear-phishing, password-spray, and brute-force password attacks using [Attack simulation training](attack-simulation-training.md) (included with [Office 365 Threat Intelligence](office-365-ti.md).</li><li>Look for sharing risk by reviewing the built-in reports in Defender for Cloud Apps (on the Investigate tab).</li><li>Check [Compliance Manager](../../compliance/compliance-manager.md) to review status for regulations that apply to your organization (such as GDPR, NIST 800-171).</li></ul>| -|Threat protection|Implement enhanced protections for admin accounts: <ul><li>Configure [Privileged Access Workstations](/security/compass/privileged-access-devices) (PAWs) for admin activity.</li><li>Configure [Azure AD Privileged Identity Management](/azure/active-directory/active-directory-privileged-identity-management-configure).</li><li>Configure a security information and event management (SIEM) tool to collect logging data from Office 365, Defender for Cloud Apps, and other services, including AD FS. The audit log stores data for only 90 days. Capturing this data in SIEM tool allows you to store data for a longer period.</li></ul>| -|Identity and access management|<ul><li>Enable and enforce MFA for all users.</li><li>Implement a set of [conditional access and related policies](microsoft-365-policies-configurations.md).</li></ul>| -|Information protection| Adapt and implement information protection policies. These resources include examples: <ul><li>[Office 365 Information Protection for GDPR](/compliance/regulatory/gdpr)</li><li>[Configure Teams with three tiers of protection](../../solutions/configure-teams-three-tiers-protection.md)</li></ul> <p> Use data loss prevention policies and monitoring tools in Microsoft Purview for data stored in Microsoft 365 (instead of Defender for Cloud Apps). <p> Use Defender for Cloud Apps with Microsoft 365 for advanced alerting features (other than data loss prevention).| --## Beyond -<a name="Beyond"> </a> --These are important security measures that build on previous work. --|Area|Task| -||| -|Security management|<ul><li>Continue planning next actions by using Secure Score (<https://security.microsoft.com/securescore>).</li><li>Continue to regularly review dashboards and reports in the Microsoft 365 Defender portal, Defender for Cloud Apps, and SIEM tools.</li><li>Continue to look for and implement software updates.</li><li>Integrate eDiscovery into your legal and threat response processes.</li></ul>| -|Threat protection|<ul><li>Implement [Secure Privileged Access](/windows-server/identity/securing-privileged-access/securing-privileged-access) (SPA) for identity components on premises (AD, AD FS).</li><li>Use Defender for Cloud Apps to monitor for insider threats.</li><li>Discover shadow IT SaaS usage by using Defender for Cloud Apps.</li></ul>| -|Identity and access management|<ul><li>Refine policies and operational processes.</li><li>Use Azure AD Identity Protection to identify insider threats.</li></ul>| -|Information protection|Refine information protection policies: <ul><li>Microsoft 365 and Office 365 sensitivity labels and data loss prevention (DLP), or Azure Information Protection.</li><li>Defender for Cloud Apps policies and alerts.</li></ul>| --Also see: [How to mitigate rapid cyberattacks such as Petya and WannaCrypt](https://cloudblogs.microsoft.com/microsoftsecure/2018/02/21/how-to-mitigate-rapid-cyberattacks-such-as-petya-and-wannacrypt/). |
security | Tenant Wide Setup For Increased Security | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/security/office-365-security/tenant-wide-setup-for-increased-security.md | -## Check Office 365 Secure Score --Office 365 Secure Score analyzes your organization's security based on your regular activities and security settings and assigns a score. Begin by taking note of your current score. Adjusting some tenant-wide settings will increase your score. The goal is not to achieve the max score, but to be aware of opportunities to protect your environment that do not negatively affect productivity for your users. See [Microsoft Secure Score](../defender/microsoft-secure-score.md). ## Tune threat management policies in the Microsoft 365 Defender portal More information: These articles and guides provide additional prescriptive information for securing your Microsoft 365 environment: -- [Microsoft security guidance for political campaigns, nonprofits, and other agile organizations](microsoft-security-guidance-for-political-campaigns-nonprofits-and-other-agile-o.md) (you can use these recommendation in any environment, especially cloud-only environments)+- [Microsoft security guidance for political campaigns, nonprofits, and other agile organizations](microsoft-security-guidance-for-political-campaigns-nonprofits-and-other-agile-o.md) (you can use these recommendations in any environment, especially cloud-only environments) - [Recommended security policies and configurations for identities and devices](microsoft-365-policies-configurations.md) (these recommendations include help for AD FS environments) |
security | User Submission | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/security/office-365-security/user-submission.md | -description: Admins can learn how identify a custom mailbox (also known as a user submissions mailbox) to collect spam and phishing messages that are reported by users. Other settings complete the reporting experience for users when they report messages. +description: Admins can learn how to identify a custom mailbox (also known as a user submissions mailbox) to collect spam and phishing messages that are reported by users. Other settings complete the reporting experience for users when they report messages. When **Microsoft Outlook Report Message button** is **On**  to upload your custom logo. + - **Display company logo**: Before you select this option, you need to follow the instructions in [Customize the Microsoft 365 theme for your organization](../../admin/setup/customize-your-organization-theme.md) to upload your custom logo. When you're finished on the **Customize confirmation message** flyout, click **Confirm**. To correctly identify the original attached messages, messages sent to the custo To specify the reason why the original attached messages were reported, messages sent to the user submissions mailbox must meet the following criteria: - The original message attachment is unmodified.+- The reported message should contain the following required headers: + - 1. X-Microsoft-Antispam-Message-Info + - 2. Message-Id + - 3. X-Ms-Exchange-Organization-Network-Message-Id + - 4. X-Ms-Exchange-Crosstenant-Id ++> [!NOTE] +> TenantId in `X-Ms-Exchange-Crosstenant-Id` should be the same as the tenant. +> +> `X-Microsoft-Antispam-Message-Info` should be a valid xmi. + - The Subject line (Envelope Title) of messages sent to the user submissions mailbox must start with one of the following prefix values: - `1|` or `Junk:`. - `2|` or `Not junk:`. |
security | View Email Security Reports | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/security/office-365-security/view-email-security-reports.md | Each exported .csv file is limited to 150,000 rows. If the data contains more th [Anti-malware protection in EOP](anti-malware-protection.md) -[Smart reports and insights in the Microsoft 365 Defender portal](reports-and-insights-in-security-and-compliance.md) - [View mail flow reports in the Microsoft 365 Defender portal](view-mail-flow-reports.md) [View reports for Defender for Office 365](view-reports-for-mdo.md) |
security | View Mail Flow Reports | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/security/office-365-security/view-mail-flow-reports.md | For more information, see [Permissions in the Security & Compliance Center](perm > [!NOTE] > Adding users to the corresponding Azure Active Directory role in the Microsoft 365 admin center gives users the required permissions in the Security & Compliance Center _and_ permissions for other features in Microsoft 365. For more information, see [About admin roles](../../admin/add-users/about-admin-roles.md). -## Related topics --[Smart reports and insights in the Security & Compliance Center](reports-and-insights-in-security-and-compliance.md) --[Mail flow insights in the Security & Compliance Center](mail-flow-insights-v2.md) --[View email security reports in the Security & Compliance Center](view-email-security-reports.md) --[View reports for Microsoft Defender for Office 365](view-reports-for-mdo.md) |
security | View Reports For Mdo | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/security/office-365-security/view-reports-for-mdo.md | For more information, see [Permissions in the Microsoft 365 Defender portal](per If you are not seeing data in your Defender for Office 365 reports, double-check that your policies are set up correctly. Your organization must have [Safe Links policies](set-up-safe-links-policies.md) and [Safe Attachments policies](set-up-safe-attachments-policies.md) defined in order for Defender for Office 365 protection to be in place. Also see [anti-spam](anti-spam-protection.md) and [anti-malware protection](anti-malware-protection.md). -## Related topics --[Smart reports and insights in the Microsoft 365 Defender portal](reports-and-insights-in-security-and-compliance.md) --[Azure AD built-in roles](/azure/active-directory/roles/permissions-reference) |
security | Virus Detection In Spo | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/security/office-365-security/virus-detection-in-spo.md | -> The built-in anti-virus capabilities are a way to help contain viruses. They aren't intended as a single point of defense against malware for your environment. We encourage all customers to investigate and implement anti-malware protection at various layers and apply best practices for securing their enterprise infrastructure. For more information about strategies and best practices, see [Security roadmap](security-roadmap.md). +> The built-in anti-virus capabilities are a way to help contain viruses. They aren't intended as a single point of defense against malware for your environment. We encourage all customers to investigate and implement anti-malware protection at various layers and apply best practices for securing their enterprise infrastructure. ## What happens if an infected file is uploaded to SharePoint Online? |
whiteboard | Index | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/whiteboard/index.md | The resources in this section help the admin in your organization to set up and ### For government +#### GCC + | If you're looking for this information | Go to this resource | |:--|:--| |Learn how to set up and manage access to Whiteboard for US Government GCC environments|[Manage access to Whiteboard - GCC](manage-whiteboard-access-gcc.md)| |Find where your Whiteboard content and data are stored in Azure and OneDrive for Business in US Government GCC environments |[Manage data for Whiteboard - GCC](manage-data-gcc.md) | |Learn about the sharing experience in Teams and how to share links to specific users in US Government GCC environments |[Manage sharing for Whiteboard - GCC](manage-sharing-gcc.md) | |Learn which clients are currently supported for Whiteboard in US Government GCC environments |[Manage clients for Whiteboard - GCC](manage-clients-gcc.md) |++#### GCC High ++| If you're looking for this information | Go to this resource | +|:--|:--| |Learn how to set up and manage access to Whiteboard for US Government GCC High environments|[Manage access to Whiteboard - GCC High](manage-whiteboard-access-gcc-high.md)| |Find where your Whiteboard content and data are stored in Azure and OneDrive for Business in US Government GCC High environments |[Manage data for Whiteboard - GCC High](manage-data-gcc-high.md) | |Learn about the sharing experience in Teams and how to share links to specific users in US Government GCC High environments |[Manage sharing for Whiteboard - GCC High](manage-sharing-gcc-high.md) | |