We will be removing the Microsoft Store for Business tab from the Microsoft Store app on Windows 10 and 11 PCs. The Microsoft Store for Business tab will continue to be available on HoloLens devices. 

Note: The retirement of Microsoft Store for Business and Education on Windows 11 was announced in 2021

When this will happen:

We’ll be gradually rolling this out to all customers on or after mid-May.

How this will affect your organization:

Users will no longer be able to see Line of Business products listed in the Microsoft Store for Business tab in Microsoft Store when this change is implemented.

We recommend adding your apps through the new Microsoft Store app experience in Intune. If an app is not available in the Microsoft Store, you will need to retrieve an app package from the vendor and install it as a line-of-business (LOB) app or Win32 app. For instructions read the following articles:

• Add Microsoft Store apps to Microsoft Intune
• Add a Windows line-of-business app to Microsoft Intune
• Add, assign, and monitor a Win32 app in Microsoft Intune

Stay tuned to the Intune Customer Success blog as we will be publishing more information about this soon.

Message ID: MC543773

The post Removal of Microsoft Store for Business tab from Microsoft Store app on Windows 10 and 11 PCs appeared first on M365 Admin.

We will be retiring the ability to filter by ‘select file name’ from Microsoft Defender for Cloud Apps. 

When this will happen:

We will begin rolling out this change in mid-May.

What you need to do to prepare:

You are receiving this message because our reporting indicates you may have activity policy using the filter ‘select file name’. You can continue using the ‘select folder name’.

Users will no longer be able to use ‘select file name’ in activity policy, when this change is implemented.

What you can do to prepare:

You may consider updating your training and documentation as appropriate.

Message ID: MC543389

The post Activity policy – filter by file name appeared first on M365 Admin.

We will be retiring the File policy/filter ‘policy’ from the MDA file policy page. Instead, we recommend the utilization of the new Malware policy governance actions, which is where we will continue to invest our development resources.

When this will happen:

We will be rolling out this change beginning in mid-May.

How this affects your organization:

You are receiving this message because our reporting indicates your organization may be using this File policy – policy filter (allows to use Policy as part of a new file policy condition. this feature was used for Malware governance actions, and now we created the solution within ‘malware policy’ conditions.

Users will no longer be able to configure or use file policies that contain the ‘policy’ filter, when this change is implemented.

What you can do to prepare:

Instead of using the current file policy, please create a new Malware policy, with the new Governance action. 

Please click Additional Information to learn more – Activity governance actions

Message ID: MC543387

The post File policy/filter ‘policy’ retirement appeared first on M365 Admin.

We recently enabled a new feature in Office 365, which allows tenant admins to assign more than one Exchange Online license per AAD user. This provides license stacking support and automatic license feature upgrades and downgrades based on the most superior Exchange Online license pack assigned to a user.

SharePoint Online and Teams, for example, have been supporting concurrent license assignments for their own services for some time now. This new feature hence helps bring the same level of support to Exchange Online.

When this will happen:

This has already been rolled out in January 2023.

How this will affect your organization:

As a tenant admin, you would still need to run reporting on license assignments and determine which users might have more than one Exchange Online license assigned. You might then elect to remove the least superior licenses from that user and send them back to the pool of unused licenses, so other users can benefit from them. This is important to understand: if two (or more) licenses are assigned, all of them are “in use” (and might be billed).

What you need to do to prepare:

This message is for your awareness and no action is needed.

Message ID: MC541151

The post Introducing Support for Concurrent Exchange Online License Assignments appeared first on M365 Admin.

Microsoft 365 admin center will soon support tracking on the usage of all Teams apps in usage reports. IT admins will have a first-hand view of monthly and daily active user counts for first-party, third-party store, and third-party line of business apps.

When this will happen:

Rollout will begin in mid-April and is expected to be complete by late April.

How this will affect your organization:

Admins will be able to monitor any active or blocked apps available for Teams users. The report will include app usage data for first-party, third-party store, and third-party tenant specific business applications. To access the new reports, go to: Microsoft 365 admin center -> Reports -> Usage ->Teams apps.

What you need to do to prepare:

There is no action required from you at this time. Please review supporting documentation at Microsoft 365 admin center activity reports and Microsoft Learn and Microsoft 365 admin center Teams app usage reports.

Message ID: MC538387

The post Microsoft 365 admin center: Teams apps Usage Tracking Soon Available within Usage reports appeared first on M365 Admin.

Microsoft Power Platform is introducing a cleanup mechanism that will automatically remove inactive developer environments from your tenant (inclusive of all entry points, including the Power Apps Maker Portal and Power Platform admin center). This change will begin rolling out in mid-April 2023 by region and will be available worldwide by the end of May 2023.

With this change, developer environments will be first disabled after 90 days of inactivity. Once the environment has been disabled for 30 days, the environment will be deleted if no action is taken by administrators.

How do I prepare for this change?

To prepare for this change, please review your developer environments and confirm whether they will be affected by this change by accessing the Power Platform admin center and reviewing the date in the last activity column. For more information on what is considered inactive, visit definition of inactivity.

To learn about the automatic cleanup process and how to recover your environment, review the following Power Platform documentation. If you require further assistance, please contact Microsoft Support.

Message ID: MC538688

The post Power Platform admin center – Automatic deletion of inactive developer environments appeared first on M365 Admin.

Starting with Edge 113, Microsoft Edge for macOS will begin using a new updater called EdgeUpdater.

Note: This change only affects Microsoft Edge on macOS.

Microsoft Edge on macOS

• Timing: Beginning with Microsoft Edge version 113 (scheduled for the week of May 4, 2023)
• Action: If you use update preferences for Microsoft Autoupdate to prevent browser updates, you will need to transition to the new EdgeUpdater UpdateDefault policy before Edge 113 to prevent future automatic updates.

How this will affect your organization:

If you do not transition before the new EdgeUpdater is deployed with Edge 113 (scheduled for the week of May 4. 2023), the new updater will default to updating Microsoft Edge automatically on your macOS devices.

What you need to do to prepare:

To maintain your desired update preferences, you will need to transition to the new EdgeUpdater UpdateDefault policy and set your preferences prior to Edge 113.

Additional information:

• See our article on Microsoft Learn
• Microsoft 365 Roadmap – Feature ID: 114512

We always value feedback and questions from our customers. Please feel free to submit either feedback or questions via Message Center.

Message ID: MC538725

The post New Microsoft Edge updater for macOS appeared first on M365 Admin.