| Category | Microsoft Docs article | Related commit history on GitHub | Change details |
|---|---|---|---|
| frontline | Shifts Connector Blue Yonder Admin Center Manage | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/frontline/shifts-connector-blue-yonder-admin-center-manage.md | ms.localizationpriority: high - M365-collaboration - m365-frontline+ - teams-1p-app-admin appliesto: - Microsoft Teams - Microsoft 365 for frontline workers You can use the [Shifts connector wizard](shifts-connector-wizard.md) (Preview) > [!IMPORTANT] > Before mapping a Blue Yonder WFM instance to a Microsoft team, check if the team has schedule entities such as shifts or time off. If the team has an existing schedule with schedule entities, [remove the schedule entities from the team](shifts-connector-wizard.md#remove-schedule-entities-from-teams-you-want-to-map) before you map a Blue Yonder WFM instance to it. If you don't remove schedule entities before mapping, you'll see duplicate shifts. -- To create a new connection instance, select **Create instance**. You'll be taken to the wizard, where you can [choose your settings and create mappings](shifts-connector-wizard.md#create-a-connection-instance).-- To change an existing connection instance, go to **Actions** and select **Edit**. You'll be taken to the wizard, where you can [update the settings and mappings](shifts-connector-wizard.md#create-a-connection-instance).-- To delete an existing connection instance, go to **Actions** and select **Delete**. You cannot undo this.+- To create a new connection instance, select **Create instance**. You're taken to the wizard, where you can [choose your settings and create mappings](shifts-connector-wizard.md#create-a-connection-instance). +- To change an existing connection instance, go to **Actions** and select **Edit**. You're taken to the wizard, where you can [update the settings and mappings](shifts-connector-wizard.md#create-a-connection-instance). +- To delete an existing connection instance, go to **Actions** and select **Delete**. You can't undo this action. - To view more details about an existing connection instance, select its name. On the details page, you'll see health information, including ongoing errors (if any), and mappings. You can also choose **Edit** to update settings in the wizard or **Back** to return to the Connector Management Console. :::image type="content" source="media/shifts-connector-blue-yonder-manage-details.png" alt-text="Screenshot of the details page for a connection, showing connector health and mappings information." lightbox="media/shifts-connector-blue-yonder-manage-details.png"::: For a complete list of error messages and how to resolve them, see [List of erro #### Edit connection instance -To **edit your connection instance settings**, you'll need to choose the data that your Shifts users can see and change. You'll be given the following options for these settings: +To **edit your connection instance settings**, choose the data that your Shifts users can see and change. You have the following options for these settings: - **Shifts users will not see provider data**: Data won't sync between Blue Yonder WFM and Shifts. <br> - **Shifts users can see provider data**: Data syncing is unidirectional from Blue Yonder WFM to Shifts. <br> To **edit your connection instance settings**, you'll need to choose the data th > > After you edit your settings, make sure you follow the steps to [Disable open shifts, open shifts requests, swap requests, and time off requests.](/microsoft-365/frontline/shifts-connector-wizard#disable-open-shifts-open-shifts-requests-swap-requests-and-time-off-requests) -To **Edit your connection instance mappings**, you'll have the choice of: +To **Edit your connection instance mappings**, you have the choice of: - Adding new mappings, by following the same process as when you first create your connection instance. See [Map Blue Yonder Workforce Management instances to teams](/microsoft-365/frontline/shifts-connector-wizard#map-blue-yonder-workforce-management-instances-to-teams)-- Edit existent mappings, to update the Microsoft Teams to which a WFM instance is connected to.- If you are mapping to team in Microsoft Teams that has previously used Shifts, make sure you [Remove schedule entities from teams you want to map](/microsoft-365/frontline/shifts-connector-wizard?#remove-schedule-entities-from-teams-you-want-to-map) -- Deleting active mappings, either by selecting to un-tick the checkbox of the WFM instance mapped, or by uploading the CSV file with the removed un-desired mapping row.-+- Edit existing mappings, to update the team in Microsoft Teams to which a WFM instance is connected. + If you're mapping to team in Microsoft Teams that has previously used Shifts, make sure you [remove schedule entities from teams you want to map](/microsoft-365/frontline/shifts-connector-wizard?#remove-schedule-entities-from-teams-you-want-to-map) +- Deleting active mappings, either by clearing the checkbox of the mapped WFM instance, or by uploading the CSV file with the mapping rows removed. ## List of error messages Here's the list of error messages that you may encounter and information to help |Error type |Error details |Resolution | |||| |Unable to authenticate workforce management system.|The workforce management system account credentials you've provided are invalid or this account doesn't have the required permissions.|Update your WFM service account credentials in the connection settings page. To do this, go to your Microsoft 365 admin center and choose **Edit** next to the connection on the Connector Management Console page.|-|Unable to authenticate Graph. |Authentication failed. Ensure that you've entered valid credentials for the designated actor and have the required permissions.|Make sure that your Microsoft 365 system account (also known as designated actor) is added as a team owner. Or, update your Microsoft 365 system account to the correct team owner. To do this, in the Microsoft 365 admin center, choose **Edit** next to the connection instance on the Connector Management Console page. You will be redirected to the wizard and, in the Sync Settings page, you can update the Microsoft 365 system account.| +|Unable to authenticate Graph. |Authentication failed. Ensure that you've entered valid credentials for the designated actor and have the required permissions.|Make sure that your Microsoft 365 system account (also known as designated actor) is added as a team owner. Or, update your Microsoft 365 system account to the correct team owner. To do this, in the Microsoft 365 admin center, choose **Edit** next to the connection instance on the Connector Management Console page. You're redirected to the wizard and, on the Sync Settings page, you can update the Microsoft 365 system account.| |Some users have failed to map correctly|Mapping failed for some users: \<X\> succeeded, \<X\> failed Azure Active Directory users and \<X\> failed workforce management system users.|Use the [Get-CsTeamsShiftsConnectionSyncResult](/powershell/module/teams/get-csteamsshiftsconnectionsyncresult) cmdlet or [this PowerShell script](shifts-connector-powershell-manage.md#user-mapping-errors) to identify the users for whom the mapping failed. Make sure that the users in the mapped team match the users in the WFM instance.|-|Unable to map a team or teams in this batch |This designated actor profile doesn't have team ownership privileges. |Make sure that your Microsoft 365 system account (also known as designated actor) is added as a team owner. Or, update your Microsoft 365 system account to the correct team owner. To do this, in the Microsoft 365 admin center, choose **Edit** next to the connection instance on the Connector Management Console page. You will be redirected to the wizard and, in the Sync Settings page, you can update the Microsoft 365 system account. | +|Unable to map a team or teams in this batch |This designated actor profile doesn't have team ownership privileges. |Make sure that your Microsoft 365 system account (also known as designated actor) is added as a team owner. Or, update your Microsoft 365 system account to the correct team owner. To do this, in the Microsoft 365 admin center, choose **Edit** next to the connection instance on the Connector Management Console page. You're redirected to the wizard and, on the Sync Settings page, you can update the Microsoft 365 system account. | | |This team is already mapped to an existing connection instance. |Unmap the team from the existing connection instance by using the [Remove-CsTeamsShiftsConnectionTeamMap](/powershell/module/teams/remove-csteamsshiftsconnectionteammap) cmdlet. Or, create a new connection to remap the team.| | |This timezone is invalid. The timezone passed in isn't using tz database format.|Make sure that the time zone is correct, and then remap the team.| | |We can't find this connection instance.|Map the team to an existing connection instance.| |
| frontline | Shifts Connector Blue Yonder Known Issues | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/frontline/shifts-connector-blue-yonder-known-issues.md | ms.localizationpriority: high - M365-collaboration - m365-frontline+ - teams-1p-app-admin appliesto: - Microsoft Teams - Microsoft 365 for frontline workers |
| frontline | Shifts Connector Blue Yonder Powershell Setup | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/frontline/shifts-connector-blue-yonder-powershell-setup.md | + - teams-1p-app-admin appliesto: - Microsoft Teams - Microsoft 365 for frontline workers |
| frontline | Shifts Connector Powershell Manage | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/frontline/shifts-connector-powershell-manage.md | + - teams-1p-app-admin appliesto: - Microsoft Teams - Microsoft 365 for frontline workers |
| frontline | Shifts Connector Ukg Admin Center Manage | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/frontline/shifts-connector-ukg-admin-center-manage.md | ms.localizationpriority: high - M365-collaboration - m365-frontline+ - teams-1p-app-admin appliesto: - Microsoft Teams - Microsoft 365 for frontline workers Last updated 3/21/2023 The [Microsoft Teams Shifts connector for UKG Dimensions](shifts-connectors.md#microsoft-teams-shifts-connector-for-ukg-dimensions) (Preview) enables you to integrate the Shifts app in Microsoft Teams with UKG Dimensions. Your frontline workers can seamlessly view and manage their schedules in UKG Dimensions from within Shifts. -You can use the [Shifts connector](shifts-connector-wizard-ukg.md) (Preview) in the Microsoft 365 admin center or [PowerShell](shifts-connector-ukg-powershell-setup.md) to create a connection and connection instances. After they're set up, you can manage them in the Microsoft 365 admin center. The Connector Management Console page lists each connection and connection instance that you've set up, along with information such as health status and sync interval details. You can also access the wizard to create a new connection and connection instances or make changes to any of your existing ones. Select the name of a connection instance to view the details of any errors. +You can use the [Shifts connector wizard](shifts-connector-wizard-ukg.md) (Preview) in the Microsoft 365 admin center or [PowerShell](shifts-connector-ukg-powershell-setup.md) to create a connection and connection instances. After they're set up, you can manage them in the Microsoft 365 admin center. The Connector Management Console page lists each connection and connection instance that you've set up, along with information such as health status and sync interval details. You can also access the wizard to create a new connection and connection instances or make changes to any of your existing ones. Select the name of a connection instance to view the details of any errors. > [!NOTE] > You can also use PowerShell to manage a connection. For example, you can view an error report, change connection settings, and disable sync. To learn more, see [Use PowerShell to manage your Shifts connection to UKG Dimensions](shifts-connector-ukg-powershell-manage.md). You can use the [Shifts connector](shifts-connector-wizard-ukg.md) (Preview) in > [!IMPORTANT] > Before mapping a UKG Dimensions instance to a Microsoft team, check if the team has schedule entities such as shifts or time off. If the team has an existing schedule with schedule entities, [remove the schedule entities from the team](shifts-connector-wizard-ukg.md#remove-schedule-entities-from-teams-you-want-to-map) before you map a UKG Dimensions instance to it. If you don't remove schedule entities before mapping, you'll see duplicate shifts. -- To create a new connection instance, select **Create instance**. You'll be taken to the wizard, where you can [choose your settings and create mappings](shifts-connector-wizard-ukg.md#create-a-connection-instance).-- To change an existing connection instance, go to **Actions** and select **Edit**. You'll be taken to the wizard, where you can [update the settings and mappings](shifts-connector-wizard-ukg.md#create-a-connection-instance).-- To delete an existing connection instance, go to **Actions** and select **Delete**. You cannot undo this.+- To create a new connection instance, select **Create instance**. You're taken to the wizard, where you can [choose your settings and create mappings](shifts-connector-wizard-ukg.md#create-a-connection-instance). +- To change an existing connection instance, go to **Actions** and select **Edit**. You're taken to the wizard, where you can [update the settings and mappings](shifts-connector-wizard-ukg.md#create-a-connection-instance). +- To delete an existing connection instance, go to **Actions** and select **Delete**. You can't undo this action. - To view more details about an existing connection instance, select its name. On the details page, you'll see health information, including ongoing errors (if any), and mappings. You can also choose **Edit** to update settings in the wizard or **Back** to return to the Connector Management Console. :::image type="content" source="media/shifts-connector-ukg-manage-details.png" alt-text="Screenshot of the details page for a connection, showing connector health and mappings information." lightbox="media/shifts-connector-ukg-manage-details.png"::: For a complete list of error messages and how to resolve them, see [List of erro #### Edit connection instance -To **edit your connection instance settings**, you'll need to choose the data that your Shifts users can see and change. You'll be given the following options for these settings: +To **edit your connection instance settings**, choose the data that your Shifts users can see and change. You have the following options for these settings: - **Shifts users will not see provider data**: Data won't sync between UKG Dimensions and Shifts. <br> - **Shifts users can see provider data**: Data syncing is unidirectional from UKG Dimensions to Shifts. <br> To **edit your connection instance settings**, you'll need to choose the data th > > After you edit your settings, make sure you follow the steps to [Disable open shifts, open shifts requests, swap requests, and time off requests.](/microsoft-365/frontline/shifts-connector-wizard-ukg#disable-open-shifts-open-shifts-requests-swap-requests-and-time-off-requests) -To **edit your connection instance mappings**, you'll have the choice of: +To **edit your connection instance mappings**, you have the choice of: - Adding new mappings, by following the same process as when you first create your connection instance. See [Map UKG Dimensions instances to teams](/microsoft-365/frontline/shifts-connector-wizard-ukg#map-ukg-dimensions-instances-to-teams)-- Edit existent mappings, to update the Microsoft Teams to which a WFM instance is connected to.- If you are mapping to team in Microsoft Teams that has previously used Shifts, make sure you [Remove schedule entities from teams you want to map](/microsoft-365/frontline/shifts-connector-wizard-ukg#remove-schedule-entities-from-teams-you-want-to-map) -- Deleting active mappings, either by selecting to un-tick the checkbox of the WFM instance mapped, or by uploading the CSV file with the removed un-desired mapping row.+- Edit existing mappings, to update the team in Microsoft Teams to which a WFM instance is connected. + If you're mapping to a team in Microsoft Teams that has previously used Shifts, make sure you [remove schedule entities from teams you want to map](/microsoft-365/frontline/shifts-connector-wizard-ukg#remove-schedule-entities-from-teams-you-want-to-map) +- Deleting active mappings, either by clearing the checkbox of the mapped WFM instance, or by uploading the CSV file with the mapping row removed. ## List of error messages Here's the list of error messages that you may encounter and information to help |Error type |Error details |Resolution | |||| |Unable to authenticate workforce management system.|The workforce management system account credentials you've provided are invalid or this account doesn't have the required permissions.|Update your WFM service account credentials in the connection settings page. To do this, go to your Microsoft 365 admin center and choose **Edit** next to the connection on the Connector Management Console page.|-|Unable to authenticate Graph. |Authentication failed. Ensure that you've entered valid credentials for the designated actor and have the required permissions.|Make sure that your Microsoft 365 system account (also known as designated actor) is added as a team owner. Or, update your Microsoft 365 system account to the correct team owner. To do this, in the Microsoft 365 admin center, choose **Edit** next to the connection instance on the Connector Management Console page. You will be redirected to the wizard and, in the Sync Settings page, you can update the Microsoft 365 system account.| +|Unable to authenticate Graph. |Authentication failed. Ensure that you've entered valid credentials for the designated actor and have the required permissions.|Make sure that your Microsoft 365 system account (also known as designated actor) is added as a team owner. Or, update your Microsoft 365 system account to the correct team owner. To do this, in the Microsoft 365 admin center, choose **Edit** next to the connection instance on the Connector Management Console page. You're redirected to the wizard and, in the Sync Settings page, you can update the Microsoft 365 system account.| |Some users have failed to map correctly|Mapping failed for some users: \<X\> succeeded, \<X\> failed Azure Active Directory users and \<X\> failed workforce management system users.|Use the [Get-CsTeamsShiftsConnectionSyncResult](/powershell/module/teams/get-csteamsshiftsconnectionsyncresult) cmdlet or [this PowerShell script](shifts-connector-ukg-powershell-manage.md#user-mapping-errors) to identify the users for whom the mapping failed. Make sure that the users in the mapped team match the users in the WFM instance.|-|Unable to map a team or teams in this batch |This designated actor profile doesn't have team ownership privileges. |Make sure that your Microsoft 365 system account (also known as designated actor) is added as a team owner. Or, update your Microsoft 365 system account to the correct team owner. To do this, in the Microsoft 365 admin center, choose **Edit** next to the connection instance on the Connector Management Console page. You will be redirected to the wizard and, in the Sync Settings page, you can update the Microsoft 365 system account. | +|Unable to map a team or teams in this batch |This designated actor profile doesn't have team ownership privileges. |Make sure that your Microsoft 365 system account (also known as designated actor) is added as a team owner. Or, update your Microsoft 365 system account to the correct team owner. To do this, in the Microsoft 365 admin center, choose **Edit** next to the connection instance on the Connector Management Console page. You're redirected to the wizard and, in the Sync Settings page, you can update the Microsoft 365 system account. | | |This team is already mapped to an existing connection instance. |Unmap the team from the existing connection instance by using the [Remove-CsTeamsShiftsConnectionTeamMap](/powershell/module/teams/remove-csteamsshiftsconnectionteammap) cmdlet. Or, create a new connection to remap the team. | | |This timezone is invalid. The timezone passed in isn't using tz database format. |Make sure that the time zone is correct, and then remap the team.| | |This connection instance couldn't be found.|Map the team to an existing connection instance.| |
| frontline | Shifts Connector Ukg Known Issues | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/frontline/shifts-connector-ukg-known-issues.md | ms.localizationpriority: high - M365-collaboration - m365-frontline+ - teams-1p-app-admin appliesto: - Microsoft Teams - Microsoft 365 for frontline workers |
| frontline | Shifts Connector Ukg Powershell Manage | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/frontline/shifts-connector-ukg-powershell-manage.md | ms.localizationpriority: high - M365-collaboration - m365-frontline+ - teams-1p-app-admin appliesto: - Microsoft Teams - Microsoft 365 for frontline workers |
| frontline | Shifts Connector Ukg Powershell Setup | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/frontline/shifts-connector-ukg-powershell-setup.md | ms.localizationpriority: high - M365-collaboration - m365-frontline+ - teams-1p-app-admin appliesto: - Microsoft Teams - Microsoft 365 for frontline workers |
| frontline | Shifts Connector Wizard Ukg | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/frontline/shifts-connector-wizard-ukg.md | ms.localizationpriority: high - M365-collaboration - m365-frontline+ - teams-1p-app-admin appliesto: - Microsoft Teams - Microsoft 365 for frontline workers |
| frontline | Shifts Connector Wizard | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/frontline/shifts-connector-wizard.md | + - teams-1p-app-admin appliesto: - Microsoft Teams - Microsoft 365 for frontline workers |
| frontline | Shifts Connectors | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/frontline/shifts-connectors.md | + - teams-1p-app-admin appliesto: - Microsoft Teams - Microsoft 365 for frontline workers |
| frontline | Shifts For Teams Landing Page | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/frontline/shifts-for-teams-landing-page.md | + - teams-1p-app-admin search.appverid: MET150 ms.localizationpriority: high searchScope: |
| frontline | Virtual Appointments App | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/frontline/virtual-appointments-app.md | - - m365-virtual-appointments + - m365-virtual-appointments + - teams-1p-app-admin description: Get an overview of how to use the Virtual Appointments app in Teams to schedule, manage, conduct and view analytics on virtual appointments in your organization. appliesto: |
| security | Configure Endpoints Script | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/security/defender-endpoint/configure-endpoints-script.md | description: Use a local script to deploy the configuration package on devices t keywords: configure devices using a local script, device management, configure Microsoft Defender for Endpoint devices search.appverid: met150 -ms.sitesec: library -ms.pagetype: security ms.localizationpriority: medium Check out [Identify Defender for Endpoint architecture and deployment method](de ## Onboard devices -1. Open the GP configuration package .zip file (*WindowsDefenderATPOnboardingPackage.zip*) that you downloaded from the service onboarding wizard. You can also get the package from <a href="https://go.microsoft.com/fwlink/p/?linkid=2077139" target="_blank">Microsoft 365 Defender portal</a>: +1. Open the configuration package .zip file (*WindowsDefenderATPOnboardingPackage.zip*) that you downloaded from the service onboarding wizard. You can also get the package from <a href="https://go.microsoft.com/fwlink/p/?linkid=2077139" target="_blank">Microsoft 365 Defender portal</a>: 1. In the navigation pane, select **Settings** \> **Endpoints** \> **Device management** \> **Onboarding**. 2. Select Windows 10 or Windows 11 as the operating system. 3. In the **Deployment method** field, select **Local Script**. Check out [Identify Defender for Endpoint architecture and deployment method](de 5. Press the **Enter** key or click **OK**. +6. Type "Y" and enter when prompted. ++7. After the script completes, it will display "Press any key to continue...". Press any key to complete the steps on the device. + For information on how you can manually validate that the device is compliant and correctly reports sensor data see, [Troubleshoot Microsoft Defender for Endpoint onboarding issues](troubleshoot-onboarding.md). > [!TIP] Monitoring can also be done directly on the portal, or by using the different de ### Monitor devices using the portal 1. Go to <a href="https://go.microsoft.com/fwlink/p/?linkid=2077139" target="_blank">Microsoft 365 Defender portal</a>.+ 2. Click **Devices inventory**.+ 3. Verify that devices are appearing. -## Related topics +## Related articles - [Onboard Windows devices using Group Policy](configure-endpoints-gp.md) - [Onboard Windows devices using Microsoft Endpoint Configuration Manager](configure-endpoints-sccm.md) - [Onboard Windows devices using Mobile Device Management tools](configure-endpoints-mdm.md) |
| security | Microsoft Defender Antivirus Compatibility | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/security/defender-endpoint/microsoft-defender-antivirus-compatibility.md | description: Learn about Microsoft Defender Antivirus with other security produc ms.localizationpriority: medium Previously updated : 06/14/2023 Last updated : 09/01/2023 Defender for Endpoint affects whether Microsoft Defender Antivirus can run in pa | [Cloud-delivered protection](enable-cloud-protection-microsoft-defender-antivirus.md) | Yes | No | No | | [Network protection](network-protection.md) | Yes | No | No | | [Attack surface reduction rules](attack-surface-reduction.md) | Yes | No | No |-| [Limited periodic scanning availability](limited-periodic-scanning-microsoft-defender-antivirus.md) | No | Yes | No | | [File scanning and detection information](review-scan-results-microsoft-defender-antivirus.md) | Yes | Yes <br/>[See note 2](#notes-about-protection-states) | No | | [Threat remediation](configure-remediation-microsoft-defender-antivirus.md) | Yes | [See note 3](#notes-about-protection-states) | No | | [Security intelligence updates](microsoft-defender-antivirus-updates.md) | Yes | Yes <br/>[See note 4](#notes-about-protection-states) | No | You might also use [limited periodic scanning](limited-periodic-scanning-microso - [EDR in block mode](edr-in-block-mode.md) - [Learn about Endpoint data loss prevention](/microsoft-365/compliance/endpoint-dlp-learn-about) [!INCLUDE [Microsoft Defender for Endpoint Tech Community](../../includes/defender-mde-techcommunity.md)]+ |
| security | Anti Malware Protection About | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/security/office-365-security/anti-malware-protection-about.md | description: Admins can learn about anti-malware protection and anti-malware pol Previously updated : 8/22/2023 Last updated : 9/1/2023 appliesto: - ✅ <a href="https://learn.microsoft.com/microsoft-365/security/office-365-security/eop-about" target="_blank">Exchange Online Protection</a> - ✅ <a href="https://learn.microsoft.com/microsoft-365/security/office-365-security/microsoft-defender-for-office-365-product-overview#microsoft-defender-for-office-365-plan-1-vs-plan-2-cheat-sheet" target="_blank">Microsoft Defender for Office 365 plan 1 and plan 2</a> You can only use a condition or exception once, but the condition or exception c There are certain types of files that you really shouldn't send via email (for example, executable files). Why bother scanning these types of files for malware, when you should probably block them all, anyway? That's where the common attachments filter comes in. The file types that you specify are automatically treated as malware. -- The default file types: `ace, apk, app, appx, ani, arj, bat, cab, cmd,com, deb, dex, dll, docm, elf, exe, hta, img, iso, jar, jnlp, kext, lha, lib, library, lnk, lzh, macho, msc, msi, msix, msp, mst, pif, ppa, ppam, reg, rev, scf, scr, sct, sys, uif, vb, vbe, vbs, vxd, wsc, wsf, wsh, xll, xz, z`.+A list of file types is specified by default. You can select from a list of additional file types when you create or modify anti-malware policies in the Microsoft 365 Defender portal. -- Additional predefined file types that you can select from in the Microsoft 365 Defender portal<sup>\*</sup>: `7z, 7zip, a, accdb, accde, action, ade, adp, appxbundle, asf, asp, aspx, avi, bin, bundle, bz, bz2, bzip2, cab, caction, cer, chm, command, cpl, crt, csh, css, der, dgz, dmg, doc, docx, dot, dotm, dotx, dylib, font, gz, gzip, hlp, htm, html, imp, inf, ins, ipa, isp, its, jnlp, js, jse, ksh, lqy, mad, maf, mag, mam, maq, mar, mas, mat, mav, maw, mda, mdb, mde, mdt, mdw, mdz, mht, mhtml, mscompress, msh, msh1, msh1xml, msh2, msh2xml, mshxml, msixbundle, o, obj, odp, ods, odt, one, onenote, ops, package, pages, pbix, pdb, pdf, php, pkg, plugin, pps, ppsm, ppsx, ppt, pptm, pptx, prf, prg, ps1, ps1xml, ps2, ps2xml, psc1, psc2, pst, pub, py, rar, rpm, rtf, scpt, service, sh, shb, shtm, shx, so, tar, tarz, terminal, tgz, tool, url, vhd, vsd, vsdm, vsdx, vsmacros, vss, vssx, vst, vstm, vstx, vsw, workflow, ws, xhtml, xla, xlam, xls, xlsb, xlsm, xlsx, xlt, xltm, xltx, zi, zip, zipx`.+Using the Defender portal or the _FileTypes_ parameter in the [New-MalwareFilterPolicy](/powershell/module/exchange/new-malwarefilterpolicy) or [Set-MalwareFilterPolicy](/powershell/module/exchange/set-malwarefilterpolicy) cmdlets in Exchange Online PowerShell, you can add any text value as an additional file type or remove existing file types when you create or modify anti-malware policies. -<sup>\*</sup> You can enter any text value in the Defender portal or using the _FileTypes_ parameter in the [New-MalwareFilterPolicy](/powershell/module/exchange/new-malwarefilterpolicy) or [Set-MalwareFilterPolicy](/powershell/module/exchange/set-malwarefilterpolicy) cmdlets in Exchange Online PowerShell. +- **Default file types**: `ace, ani, apk, app, appx, arj, bat, cab, cmd, com, deb, dex, dll, docm, elf, exe, hta, img, iso, jar, jnlp, kext, lha, lib, library, lnk, lzh, macho, msc, msi, msix, msp, mst, pif, ppa, ppam, reg, rev, scf, scr, sct, sys, uif, vb, vbe, vbs, vxd, wsc, wsf, wsh, xll, xz, z`. ++- **Additional file types to select in the Defender portal**: `7z, 7zip, a, accdb, accde, action, ade, adp, appxbundle, asf, asp, aspx, avi, bas, bin, bundle, bz, bz2, bzip2, caction, cer, chm, command, cpl, crt, csh, css, der, dgz, dmg, doc, docx, dos, dot, dotm, dtox, dylib, font, fxp, gadget, gz, gzip, hlp, Hta, htm, html, imp, inf, ins, ipa, isp, its, js, jse, ksh, Lnk, lqy, mad, maf, mag, mam, maq, mar, mas, mat, mau, mav, maw, mda, mdb, mde, mdt, mdw, mdz, mht, mhtml, mscompress, msh, msh1, msh1xml, msh2, msh2xml, mshxml, msixbundle, o, obj, odp, ods, odt, one, onenote, ops, os2, package, pages, pbix, pcd, pdb, pdf, php, pkg, plg, plugin, pps, ppsm, ppsx, ppt, pptm, pptx, prf, prg, ps1, ps1xml, ps2, ps2xml, psc1, psc2, pst, pub, py, rar, rpm, rtf, scpt, service, sh, shb, shs, shtm, shx, so, tar, tarz, terminal, tgz, tmp, tool, url, vhd, vsd, vsdm, vsdx, vsmacros, vss, vssx, vst, vstm, vstx, vsw, w16, workflow, ws, xhtml, xla, xlam, xls, xlsb, xlsm, xlsx, xlt, xltm, xltx, xnk, zi, zip, zipx`. When files are detected by the common attachments filter, you can choose to **Reject the message with a non-delivery report (NDR)** or **Quarantine the message**. The common attachments filter uses best effort true type matching to detect the True type matching in the common attachments filter supports the following file types: -`7zip, ace, adoc, ani, arc, arj, asf, asice, avi, bmp, bz, bz2, cab, cda, chm, deb, dex, dll, dmg, doc, docm, docx, dot, dotm, dotx, dwg, eml, eps, epub, excelml, exe, fluid, gif, gzip, heic, heif, html, hyper, icon, ics, infopathml, jar, javabytecode, jnlp, jpeg, json,lib, lnk, lzh, lzma, macho, mhtml, mp3, mp4, mpeg, mpp, msaccess, mscompress, msg, msp, musx, nws, obd, obj, obt, odbcexcel, odc, odf, odg, odi, odm, odp, ods, odt, one, otc, otf, otg, oth, oti, otp, ots, ott, pal, pcx, pdf, pfb, pfile, pif, png, pointpub, pot, potm, potx, powerpointml, ppam, pps, ppsm, ppsx, ppt, pptm, pptx, ps, pub, qcp, quicktime, rar, rar4, riff, rmi, rpm, rpmsg, rtf, smime, swf,tar, tiff, tlb, tnef, ttf, txt, vcf, vcs, vdw, vdx, vsd, vsdm, vsdx, vss, vssm, vssx, vst, vstm, vstx, vsx, vtt, vtx, wav, webp, whiteboard, wmf, woff, woff2, word2, wordml, xar, xlam, xlb, xlc, xls, xlsb, xlsm, xlsx, xlt, xltm, xltx, xml, xps, xz, z, zip, zoo` +`7zip, ace, adoc, ani, arc, arj, asf, asice, avi, bmp, bz, bz2, cab, cda, chm, deb, dex, dll, dmg, doc, docm, docx, dot, dotm, dotx, dwg, eml, eps, epub, excelml, exe, fluid, gif, gzip, heic, heif, html, hyper, icon, ics, infopathml, jar, javabytecode, jnlp, jpeg, json, lib, lnk, lzh, lzma, macho, mhtml, mp3, mp4, mpeg, mpp, msaccess, mscompress, msg, msp, musx, nws, obd, obj, obt, odbcexcel, odc, odf, odg, odi, odm, odp, ods, odt, one, otc, otf, otg, oth, oti, otp, ots, ott, pal, pcx, pdf, pfb, pfile, pif, png, pointpub, pot, potm, potx, powerpointml, ppam, pps, ppsm, ppsx, ppt, pptm, pptx, ps, pub, qcp, quicktime, rar, rar4, riff, rmi, rpm, rpmsg, rtf, smime, swf, tar, tiff, tlb, tnef, ttf, txt, vcf, vcs, vdw, vdx, vsd, vsdm, vsdx, vss, vssm, vssx, vst, vstm, vstx, vsx, vtt, vtx, wav, webp, whiteboard, wmf, woff, woff2, word2, wordml, xar, xlam, xlb, xlc, xls, xlsb, xlsm, xlsx, xlt, xltm, xltx, xml, xps, xz, z, zip, zoo` If true type matching fails or isn't supported for the file type, then simple extension matching is used. |
| security | Anti Spam Spam Vs Bulk About | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/security/office-365-security/anti-spam-spam-vs-bulk-about.md | EmailEvents | summarize count() by SenderMailFromAddress, BulkComplaintLevel ``` -This query allows admins to identify wanted and unwanted senders. If a bulk sender has a BCL score that's less than the bulk threshold, admins can [report the sender's messages to Microsoft for analysis](submissions-admin.md#report-good-email-to-microsoft). This action also adds the sender as an allow entry in the Tenant Allow/Block List. +This query allows admins to identify wanted and unwanted senders. If a bulk sender has a BCL score that's more than the bulk threshold, admins can [report the sender's messages to Microsoft for analysis](submissions-admin.md#report-good-email-to-microsoft). This action also adds the sender as an allow entry in the Tenant Allow/Block List. Organizations without Defender for Office 365 Plan 2 can try the features in Microsoft 365 Defender for Office 365 Plan 2 for free. Use the 90-day Defender for Office 365 evaluation at <https://security.microsoft.com/atpEvaluation>. Learn about who can sign up and trial terms [here](try-microsoft-defender-for-office-365.md) or you can use the [Threat protection status report](reports-email-security.md#threat-protection-status-report) to identify wanted and unwanted bulk senders: |