2023 CW 29 Microsoft 365 Message Center changes

If your organization has Stream live events scheduled beyond September 15, 2023, please reschedule those events. Any Stream live events scheduled after September 15, 2023 will be automatically removed.

For more information see the links below:

Stream live events replacement service FAQs

How to set up a Teams live event

How to produce a Teams live event

Teams live events capabilities and limitations

If your organization has Stream live events scheduled beyond September 15, 2023, please reschedule those events. Any Stream live events scheduled after September 15, 2023 will be automatically removed.

For more information see the links below:

Stream live events replacement service FAQs

How to set up a Teams live event

How to produce a Teams live event

Teams live events capabilities and limitations

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.

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.

Channel:

Note: Search capability on the new Channels experience is currently available on the main view, and we will extend it to the conversation view very soon.

In addition to the keyboard shortcut, a dedicated button ‘Find in Channel’, placed on the channel info pane can be used to initiate contextual search:

Note: we are working on bring the search entry point to the chat surface soon.

We now have introduced enhanced captioning and keyword highlighting to aid the discernment of results in chat and channel:

4. In-chat search will now also be available in pop-out chats.

Intune What's new 2306(June) Blog

Staying up to date on Intune new features, service changes, and service health

Where can I learn more?

For more information on the Modern Security Role Editor User Interface and its capabilities, click here.

[What you need to do to prepare:

No specific action is required as this will be available to all Teams users and not gated by an admin policy.

What do I need to prepare for this change?

You can inform your IT staff and helpdesk of the upcoming changes listed on this page. Plan to update your user guidance, if you feel any of these features would be important to your users.

Additional Information

Intune In development

As the List Flows as Admin action has been deprecated, we will be monitoring usage levels for the deprecated List flows as Admin action and its supporting API. Starting August 2023, we will evaluate the migration progress to List Flows as Admin (V2) action and begin enforcing the deprecation at runtime. This will cause the calls to the backing API of List Flows as Admin to fail at runtime and, in time, impact the older PowerShell cmdlet versions, older Center of Excellence Starter Kit versions, and calls to the deprecated List flows as Admin action.

For additional details and support please see the community forum post Transition to List Flows as Admin V2. The forum post will be monitored for questions.

What actions do I need to take?

Transition to using the List Flows as Admin (V2) action for your new and existing flows. Existing flows can be found with the PowerShell script in Transition to List Flows as Admin V2.

If you have the COE Starter Kit installed, update COE Starter Kit to the latest release.

If you use PowerShell, update the Microsoft.PowerApps.Administration.PowerShell module.

Learn more about the name change for Azure AD

Read the blog about the latest Microsoft Entra announcements

Resources:

Learn more about the name change for Azure AD

Read the blog about the latest Microsoft Entra announcements

For organizations with users around the globe, we recognize that "outside of normal business hours" might affect you differently. We apologize for the impact this may have on your users. We are working hard to improve Viva Goals, to minimize these maintenance windows.

This message is specifically associated with post-meeting transcripts access for apps - Microsoft 365 Roadmap ID: 95788 that allows authorized apps to access Teams Meetings transcripts once the meeting is over.

[When will this happen?]

This API will be published to beta in end of July 2022 and to GA in mid-June (previously early April)

This message is specifically associated with post-meeting transcripts access for apps - Microsoft 365 Roadmap ID: 95788 that allows authorized apps to access Teams Meetings transcripts once the meeting is over.

[When will this happen?]

We will begin rolling this out in mid-August (previously mid-June) and expect to complete early September.

Note: The rebuilt Stream mobile app will lack certain features that may be critical to some users, such as video recording, uploading and offline downloads. As we continue to build out the revamped mobile app, we expect to add these features in 2023.

[Timeline and Scope]

As we have communicated multiple times over the past few years and with multiple Message center posts, we began to turn off Basic authentication for several protocols in our worldwide multi-tenant service on October 1, 2022.

Next, we intend to block Basic auth to the Autodiscover service, which is typically used by Outlook, Exchange ActiveSync, and Exchange Web Services apps to help them automatically configure and connect.

Once Basic auth is disabled in your tenant, there’s no reason to keep Autodiscover Basic auth enabled, so we plan on disabling it to further protect your tenant. We will do this during the next few months. If you re-enabled Basic auth in your tenant, or took the option to request more time, we’ll turn off Autodiscover after that extension has expired.

[Timeline and Scope]

To ensure that these notifications successfully reach you, an email will now be sent automatically each time a new issue is posted.

If you do not want to receive these email notifications, you can adjust your email preferences by clicking the "Customize" button on the service health page.

This message is associated with Microsoft 365 Roadmap ID 103631

[When this will happen:]

Targeted Release: We will begin rolling out mid-June (previously early May) and expect to complete by early July (previously mid-May).

Standard Release: We will begin rolling out early July (previously late May) and expect to complete by late July (previously mid-June).

To ensure that these notifications successfully reach you, an email will now be sent automatically each time a new issue is posted.

If you do not want to receive these email notifications, you can adjust your email preferences by clicking the "Customize" button on the service health page.

This message is associated with Microsoft 365 Roadmap ID 103631

[When this will happen:]

Targeted Release: We will begin rolling out late July (previously mid-June) and expect to complete by mid-August (previously early July).

Standard Release: We will begin rolling out early August (previously early July) and expect to complete by early September (previously late July).

This message is associated with Microsoft 365 Roadmap ID 109526.

[When will this happen:]

We will begin rolling out this feature in late May (previously late April) and expect to complete the rollout in late June (previously early May).

This message is associated with Microsoft 365 Roadmap ID 109526.

[When will this happen:]

We will begin rolling out this feature in late May (previously late April) and expect to complete the rollout in late June (previously early May).

IT / Security Admin: Utilize the sign-in report described in the Identifying IPv6 traffic with Azure AD Sign-in activity reports. Use the resulting address list to determine if any IPv6 ranges need to be added to your Azure AD Security Named locations, following the steps provided. It’s also important to collaborate with your internal networking teams to verify IPv6 ranges for your organization, as required.

Network admin: Collaborate with your IT/Security admin to identify known IPv6 ranges in your network infrastructure. Add these ranges to your tenant’s existing Azure AD Named locations by following the steps provided.

We will continue to roll out IPv6 across all Azure AD regions until the end of June 2023.

Earlier, we had announced our plan to bring IPv6 support to Microsoft Azure Active Directory (Azure AD) enabling our customers to reach the Azure AD services over IPv4, IPv6 or dual stack endpoints. This is just a reminder that we’ll begin introducing IPv6 support into Azure AD services in a phased approach, starting March 31st, 2023.

If your networks don’t support IPv6, you don’t need to take any action to change your configurations or policies. For most customers, IPv4 won't completely disappear from their digital landscape, so we aren't planning to require IPv6 or to de-prioritize IPv4 in any Azure AD features or services. We will continue to share additional guidance on IPv6 enablement in Azure AD at this easy to remember link https://aka.ms/azureadipv6.

With the growing adoption and support of IPv6 across enterprise networks, service providers, and devices, many customers are wondering if their users can continue to access their services and applications from IPv6 clients and IPv6 networks.

Today, we’re excited to announce our plan to bring IPv6 support to Microsoft Azure Active Directory (Azure AD). This will allow customers to reach the Azure AD services over both IPv4 and IPv6 network protocols (dual stack).

For most customers, IPv4 won't completely disappear from their digital landscape, so we aren't planning to require IPv6 or to de-prioritize IPv4 in any Azure Active Directory features or services.

[When this will happen:]

We’ve been gradually rolling out IPv6 for some of our services for a while. Starting in late March 2023 we'll begin enabling IPv6 for Azure AD authentication. We will introduce IPv6 support into Azure AD authentication in a phased approach, beginning late March 2023.

IT / Security Admin: Utilize the sign-in report described in the Identifying IPv6 traffic with Azure AD Sign-in activity reports. Use the resulting address list to determine if any IPv6 ranges need to be added to your Azure AD Security Named locations, following the steps provided. It’s also important to collaborate with your internal networking teams to verify IPv6 ranges for your organization, as required.

Network admin: Collaborate with your IT/Security admin to identify known IPv6 ranges in your network infrastructure. Add these ranges to your tenant’s existing Azure AD Named locations by following the steps provided.

We will continue to roll out IPv6 across all Azure AD regions until the end of June 2023.

Earlier, we had announced our plan to bring IPv6 support to Microsoft Azure Active Directory (Azure AD) enabling our customers to reach the Azure AD services over IPv4, IPv6 or dual stack endpoints. This is just a reminder that we’ll begin introducing IPv6 support into Azure AD services in a phased approach, starting March 31st, 2023.

If your networks don’t support IPv6, you don’t need to take any action to change your configurations or policies. For most customers, IPv4 won't completely disappear from their digital landscape, so we aren't planning to require IPv6 or to de-prioritize IPv4 in any Azure AD features or services. We will continue to share additional guidance on IPv6 enablement in Azure AD at this easy to remember link https://aka.ms/azureadipv6.

With the growing adoption and support of IPv6 across enterprise networks, service providers, and devices, many customers are wondering if their users can continue to access their services and applications from IPv6 clients and IPv6 networks.

Today, we’re excited to announce our plan to bring IPv6 support to Microsoft Azure Active Directory (Azure AD). This will allow customers to reach the Azure AD services over both IPv4 and IPv6 network protocols (dual stack).

For most customers, IPv4 won't completely disappear from their digital landscape, so we aren't planning to require IPv6 or to de-prioritize IPv4 in any Azure Active Directory features or services.

[When this will happen:]

We’ve been gradually rolling out IPv6 for some of our services for a while. Starting in late March 2023 we'll begin enabling IPv6 for Azure AD authentication. We will introduce IPv6 support into Azure AD authentication in a phased approach, beginning late March 2023.

[When this will happen:]

Preview: We will begin rolling out in early March and expect to complete rollout by late March.

Standard Release: We will begin rolling out in early April and expect to complete rollout by early July (previously late April).

[When this will happen:]

Preview: We will begin rolling out in early March and expect to complete rollout by late March.

Standard Release: We will begin rolling out in early April and expect to complete rollout by late July (previously early July).

[When this will happen:]

Preview: We will begin rolling out in early March and expect to complete rollout by late March.

Standard Release: We will begin rolling out in early April and expect to complete rollout by early July (previously late April).

[When this will happen:]

Preview: We will begin rolling out in early March and expect to complete rollout by late March.

Standard Release: We will begin rolling out in early April and expect to complete rollout by late July (previously early July).

Standard Release: We will begin rolling out in late June (previously early May) and expect to complete rollout by early July (previously mid-May).

Standard Release: We will begin rolling out in mid-July (previously late June) and expect to complete rollout by early August (previously early July).

Standard Release: We will begin rolling out in late June (previously early May) and expect to complete rollout by early July (previously mid-May).

Standard Release: We will begin rolling out in mid-July (previously late June) and expect to complete rollout by early August (previously early July).

We always recommend having users download Authenticator to complete their sign-ins, where we can offer the most up-to-date security features. However, users that have not downloaded the app to their device can now approve authentication requests and receive TOTP codes in Outlook, bringing the security of Authenticator to a convenient location.

Admins can enable this feature by leveraging the Authentication Methods policy in Azure Active Directory.

This message is associated with Microsoft 365 Roadmap ID 122289

[When this will happen:]

Rollout of this feature in Outlook will begin in early March, starting public preview. Feature controls are available via MS Graph.

This feature will move to general availability in mid-May 2023

On June 9th, this feature will be enabled for all users by default unless admins have taken action to disable or enable it before then. Any settings configured before June 9th will not be changed.

[What you need to do to prepare:}

Starting mid-March, you can choose to enable this preview for your users from Azure Active Directory. We highly recommend that you enable users that are not already using the Microsoft Authenticator app (or another strong authentication method) for this feature at the start of public preview. This feature brings a security enhancement to those users still using telecom transports to authenticate.

This feature will roll out to tenants in the state ‘Microsoft managed’. For the duration of public preview, leaving the feature set to ‘Microsoft managed’ will have no impact on your users and the feature will remain turned off. In April 2023, we will remove preview tags and enter general availability. At GA, 'Microsoft managed' will remain set to disabled and there will be no tenant impact. On June 9th 2023, if the feature is still set to ‘Microsoft managed’, your tenant will be eligible to be enabled for this feature by Microsoft, as 'Microsoft managed' will be set to enabled. If you do not wish for this feature to be enabled on June 9th, move the state to ‘disabled’ or set users to include and exclude group prior to June 9th.

We always recommend having users download Authenticator to complete their sign-ins, where we can offer the most up-to-date security features. However, users that have not downloaded the app to their device can now approve authentication requests and receive TOTP codes in Outlook, bringing the security of Authenticator to a convenient location.

Admins can enable this feature by leveraging the Authentication Methods policy in Azure Active Directory.

This message is associated with Microsoft 365 Roadmap ID 122289

[When this will happen:]

Rollout of this feature in Outlook will begin in early March, starting public preview. Feature controls are available via MS Graph.

This feature will move to general availability in mid-May 2023

On June 9th, this feature will be enabled for all users by default unless admins have taken action to disable or enable it before then. Any settings configured before June 9th will not be changed.

[What you need to do to prepare:}

Starting mid-March, you can choose to enable this preview for your users from Azure Active Directory. We highly recommend that you enable users that are not already using the Microsoft Authenticator app (or another strong authentication method) for this feature at the start of public preview. This feature brings a security enhancement to those users still using telecom transports to authenticate.

This feature will roll out to tenants in the state ‘Microsoft managed’. For the duration of public preview, leaving the feature set to ‘Microsoft managed’ will have no impact on your users and the feature will remain turned off. In April 2023, we will remove preview tags and enter general availability. At GA, 'Microsoft managed' will remain set to disabled and there will be no tenant impact. On June 9th 2023, if the feature is still set to ‘Microsoft managed’, your tenant will be eligible to be enabled for this feature by Microsoft, as 'Microsoft managed' will be set to enabled. If you do not wish for this feature to be enabled on June 9th, move the state to ‘disabled’ or set users to include and exclude group prior to June 9th.

This message is associated with Microsoft 365 Roadmap ID: 114938

[When this will happen:]

Targeted Release and Preview: We will begin rolling out in late July (previously mid-June) and expect to complete rollout by late August (previously late June).

Standard Release: We will begin rolling out in late August (previously late June) and expect to complete rollout by early September (previously early July).

GCC, GCC-H, DoD: We will begin rolling out in early September (previously early July) and expect to complete rollout by late September (previously late July).

This message is associated with Microsoft 365 Roadmap ID: 114938

[When this will happen:]

Targeted Release and Preview: We will begin rolling out in late July (previously mid-June) and expect to complete rollout by early August (previously late June).

Standard Release: We will begin rolling out in early August (previously late June) and expect to complete rollout by early September (previously early July).

GCC, GCC-H, DoD: We will begin rolling out in early September (previously early July) and expect to complete rollout by late September (previously late July).

This message is associated with Microsoft 365 Roadmap ID: 114938

[When this will happen:]

Targeted Release and Preview: We will begin rolling out in late July (previously mid-June) and expect to complete rollout by late August (previously late June).

Standard Release: We will begin rolling out in late August (previously late June) and expect to complete rollout by early September (previously early July).

GCC, GCC-H, DoD: We will begin rolling out in early September (previously early July) and expect to complete rollout by late September (previously late July).

This message is associated with Microsoft 365 Roadmap ID: 114938

[When this will happen:]

Targeted Release and Preview: We will begin rolling out in late July (previously mid-June) and expect to complete rollout by early August (previously late June).

Standard Release: We will begin rolling out in early August (previously late June) and expect to complete rollout by early September (previously early July).

GCC, GCC-H, DoD: We will begin rolling out in early September (previously early July) and expect to complete rollout by late September (previously late July).

We're also introducing Video Capture and Upload on Android: this will allow users to capture a video on their phone within the Outlook Mobile app and seamlessly upload the video to the email being composed. Upload will leverage OneDrive for Business, allowing the user to share videos of large size and length with OneDrive.

This message is associated with Microsoft 365 Roadmap ID 117588 and 117586

[When this will happen:]

This rollout is underway and expected to complete by early July (previously late June).

We're also introducing Video Capture and Upload on Android: this will allow users to capture a video on their phone within the Outlook Mobile app and seamlessly upload the video to the email being composed. Upload will leverage OneDrive for Business, allowing the user to share videos of large size and length with OneDrive.

This message is associated with Microsoft 365 Roadmap ID 117588 and 117586

[When this will happen:]

This rollout is underway and expected to complete by late July (previously early July).

We're also introducing Video Capture and Upload on Android: this will allow users to capture a video on their phone within the Outlook Mobile app and seamlessly upload the video to the email being composed. Upload will leverage OneDrive for Business, allowing the user to share videos of large size and length with OneDrive.

This message is associated with Microsoft 365 Roadmap ID 117588 and 117586

[When this will happen:]

This rollout is underway and expected to complete by early July (previously late June).

We're also introducing Video Capture and Upload on Android: this will allow users to capture a video on their phone within the Outlook Mobile app and seamlessly upload the video to the email being composed. Upload will leverage OneDrive for Business, allowing the user to share videos of large size and length with OneDrive.

This message is associated with Microsoft 365 Roadmap ID 117588 and 117586

[When this will happen:]

This rollout is underway and expected to complete by late July (previously early July).

[When this will happen:]

Preview: We will begin rolling out end of April and expect to complete by early May.

Standard Release: We will begin rolling out late June and expect to complete by early July.

[How will this impact you:]

There is no increased risks for you. If you do not make any changes, your MTR-W will not be affected and will continue working as today.

[When this will happen:]

Preview: We will begin rolling out end of April and expect to complete by early May.

Standard Release: We will begin rolling out late June and expect to complete by early July.

[How will this impact you:]

There is no increased risks for you. If you do not make any changes, your MTR-W will not be affected and will continue working as today.

Long meetings – More than 1 hour long and 0-8 invitees

Large meetings – At least 9 invitees and at most 1 hour long

Large and long meetings – At least 9 invitees and more than 1 hour long

Recurring meetings – Meeting series with multiple instances

1:1 meetings – Include 1 other participant

These categories can help users identify meetings that are expensive in terms of time spent, participants included, or both. Using these insights, users can assess whether meetings that fall under this category are a valuable use of time and resources as a step towards doing more with less.

Categorizations will show up in Viva Insights only and will not reflect in Outlook or Teams calendar.

With this update, users who are not currently categorizing in Outlook or Teams will be able to access meeting category insights and begin developing an understanding of how their meeting time is being spent. Users who are already categorizing will receive additional insights about their meeting time allocation according to well-known meeting attributes.

This message is associated with Microsoft 365 Roadmap ID 117396

[When this will happen:]

We will begin rolling out in early July (previously late June) and complete rollout by late July (previously mid-July).

Long meetings – More than 1 hour long and 0-8 invitees

Large meetings – At least 9 invitees and at most 1 hour long

Large and long meetings – At least 9 invitees and more than 1 hour long

Recurring meetings – Meeting series with multiple instances

1:1 meetings – Include 1 other participant

These categories can help users identify meetings that are expensive in terms of time spent, participants included, or both. Using these insights, users can assess whether meetings that fall under this category are a valuable use of time and resources as a step towards doing more with less.

Categorizations will show up in Viva Insights only and will not reflect in Outlook or Teams calendar.

With this update, users who are not currently categorizing in Outlook or Teams will be able to access meeting category insights and begin developing an understanding of how their meeting time is being spent. Users who are already categorizing will receive additional insights about their meeting time allocation according to well-known meeting attributes.

This message is associated with Microsoft 365 Roadmap ID 117396

[When this will happen:]

We will begin rolling out in mid-August (previously early July) and complete rollout by mid-September (previously late July).

Long meetings – More than 1 hour long and 0-8 invitees

Large meetings – At least 9 invitees and at most 1 hour long

Large and long meetings – At least 9 invitees and more than 1 hour long

Recurring meetings – Meeting series with multiple instances

1:1 meetings – Include 1 other participant

These categories can help users identify meetings that are expensive in terms of time spent, participants included, or both. Using these insights, users can assess whether meetings that fall under this category are a valuable use of time and resources as a step towards doing more with less.

Categorizations will show up in Viva Insights only and will not reflect in Outlook or Teams calendar.

With this update, users who are not currently categorizing in Outlook or Teams will be able to access meeting category insights and begin developing an understanding of how their meeting time is being spent. Users who are already categorizing will receive additional insights about their meeting time allocation according to well-known meeting attributes.

This message is associated with Microsoft 365 Roadmap ID 117396

[When this will happen:]

We will begin rolling out in early July (previously late June) and complete rollout by late July (previously mid-July).

Long meetings – More than 1 hour long and 0-8 invitees

Large meetings – At least 9 invitees and at most 1 hour long

Large and long meetings – At least 9 invitees and more than 1 hour long

Recurring meetings – Meeting series with multiple instances

1:1 meetings – Include 1 other participant

These categories can help users identify meetings that are expensive in terms of time spent, participants included, or both. Using these insights, users can assess whether meetings that fall under this category are a valuable use of time and resources as a step towards doing more with less.

Categorizations will show up in Viva Insights only and will not reflect in Outlook or Teams calendar.

With this update, users who are not currently categorizing in Outlook or Teams will be able to access meeting category insights and begin developing an understanding of how their meeting time is being spent. Users who are already categorizing will receive additional insights about their meeting time allocation according to well-known meeting attributes.

This message is associated with Microsoft 365 Roadmap ID 117396

[When this will happen:]

We will begin rolling out in mid-August (previously early July) and complete rollout by mid-September (previously late July).

This message is associated with Microsoft 365 Roadmap ID 124259

[When this will happen:]

We will begin rolling the viewing experience to Outlook Mobile on iOS and Android to all audiences in early May and expect rollout to be complete by early July (previously late May).

This message is associated with Microsoft 365 Roadmap ID 124259

[When this will happen:]

We will begin rolling the viewing experience to Outlook Mobile on iOS and Android to all audiences in early May and expect rollout to be complete by late July (previously early July).

This message is associated with Microsoft 365 Roadmap ID 124259

[When this will happen:]

We will begin rolling the viewing experience to Outlook Mobile on iOS and Android to all audiences in early May and expect rollout to be complete by early July (previously late May).

This message is associated with Microsoft 365 Roadmap ID 124259

[When this will happen:]

We will begin rolling the viewing experience to Outlook Mobile on iOS and Android to all audiences in early May and expect rollout to be complete by late July (previously early July).

This message is associated with Microsoft 365 Roadmap ID 98121

[When this will happen:]

We will begin rolling out early June 2023 and expect to complete by late June 2023.

The compose box and recent posts will appear at the top of the page. It'll now be much easier to start a new post, keep up with the latest conversations and participate - giving users the confidence that they’ve not missed anything.

Every post is now a true conversation that users can focus on. Users can navigate to a conversation view that makes the discussion more engaging and synchronous, just like a chat. Users can also pop out the post, keep an eye on the discussion, while continuing to work on other topics.

A streamlined information pane will include all the important contextual information like channel’s members and pinned posts so new team members can quickly on-board and for all members to find the information they need, right in the channel.

Pin posts to make it easy for everyone to know what’s important in the channel and quickly reference it.

Simplified badging is making it easier for users to understand when there are new unread activities in teams. In addition, the simplified design helps users focus on the specific channels which requires the most attention, like channels in which the user was @mentioned.

This message is associated with Microsoft 365 Roadmap ID 91683

[When this will happen:]

Targeted Release: Started rolling out in May and is expected to complete in early July.

GA and GCC: We will begin rollout in late July (previously early June) and expect to complete rollout by early August (previously mid-June).

GCC-H and DoD: We will begin rollout in early August (previously mid-July) and expect to complete rollout by late August (previously late July).

The compose box and recent posts will appear at the top of the page. It'll now be much easier to start a new post, keep up with the latest conversations and participate - giving users the confidence that they’ve not missed anything.

Every post is now a true conversation that users can focus on. Users can navigate to a conversation view that makes the discussion more engaging and synchronous, just like a chat. Users can also pop out the post, keep an eye on the discussion, while continuing to work on other topics.

A streamlined information pane will include all the important contextual information like channel’s members and pinned posts so new team members can quickly on-board and for all members to find the information they need, right in the channel.

Pin posts to make it easy for everyone to know what’s important in the channel and quickly reference it.

Simplified badging is making it easier for users to understand when there are new unread activities in teams. In addition, the simplified design helps users focus on the specific channels which requires the most attention, like channels in which the user was @mentioned.

This message is associated with Microsoft 365 Roadmap ID 91683

[When this will happen:]

Targeted Release: Started rolling out in May and is expected to complete in early July.

Standard and GCC: We will begin rollout in early August (previously late July) and expect to complete rollout by mid-August (previously early August).

GCC-H and DoD: We will begin rollout in mid-August (previously early August) and expect to complete rollout by mid-September (previously late August.

In addition, mouse+keyboard multi-selection where users hold down Ctrl or Shift will continue to work as before.

This message is associated with Microsoft 365 Roadmap ID 125905

[When this will happen:]

We will begin rolling out in mid-May 2023 and expect to complete rollout by early July 2023 (previously early June).

In addition, mouse+keyboard multi-selection where users hold down Ctrl or Shift will continue to work as before.

This message is associated with Microsoft 365 Roadmap ID 125905

[When this will happen:]

We will begin rolling out in mid-May 2023 and expect to complete rollout by mid-August (previously early July 2023).

This feature provides new functionality for users who turn off folder backup (also known as “PC folder backup” and “known folder move”). When users turn off folder backup, they will have the option to restore the files back to their original location. Note: when a folder contains files stored only in the cloud, those files will not be moved; they will remain in the cloud

[When this will happen:]

Standard Release: This is currently rolling out and will complete rolling out in mid-July (previously late June).

Note: Some users may see this feature before others in your organization.

With this change, the updated Bookings Teams app will have feature parity and consistent user experience as Bookings web app. Virtual Appointments app will be a superset of the current Bookings Teams app experience embedded within the new app and will include advanced virtual appointments features.

This feature is associated with Microsoft Roadmap ID 120420

[When this will happen:]

Rollout will begin in mid-July (previously late June) and is expected to be complete by late July (previously early July).

With this change, the updated Bookings Teams app will have feature parity and consistent user experience as Bookings web app. Virtual Appointments app will be a superset of the current Bookings Teams app experience embedded within the new app and will include advanced virtual appointments features.

This feature is associated with Microsoft Roadmap ID 120420

[When this will happen:]

Rollout will begin in mid-July (previously late June) and is expected to be complete by late July (previously early July).

This change is associated with Microsoft 365 Roadmap: 124800

[When this will happen:]

The Stream (Classic) webpart will be retired on August 15, 2023.

The Stream (on SharePoint) webpart will begin its general availability roll out in early August (previously mid-June), and we expect the rollout to complete by late August (previously mid-July).

This change is associated with Microsoft 365 Roadmap: 124800

[When this will happen:]

The Stream (Classic) webpart will be retired on August 15, 2023.

The Stream (on SharePoint) webpart will begin its general availability roll out in mid-August (previously mid-June), and we expect the rollout to complete by mid-September (previously mid-July).

Rollout will begin in early June 2023 and is expected to be complete by late June 2023.

This message is associated with Microsoft 365 Roadmap ID 124897

[When this will happen:]

Rollout will begin in late June (previously early June) and is expected to be complete by late July (previously early July).

Rollout will begin at the end of June and is expected to be complete by the end of August.

This change affects items which have a Microsoft Purview retention label or legacy MRM tag auto-applied or inherited from a parent folder which is then moved to the "Deleted Items" folder either by drag & drop or manual deletion. It does not affect existing behavior for items that are 'permanently' deleted by the user (for example, using the SHIFT+DEL combination), items that have no Microsoft Purview retention labels applied, or items which have a Microsoft Purview retention label or legacy MRM tag applied manually by the user.

The enhancement includes multiple behavior changes which are summarized in the 'How this will affect your organization' section below.

[When this will happen:]

Rollout will begin at the mid-July (previously late June) and is expected to be complete by the mid-September (previously late August).

[When this will happen:]

Starting June 1, 2023.

Ending July 31, 2023.

[When this will happen:]

Starting June 1, 2023.

Ending July 31, 2023.

We will begin rolling out in mid-June and expect to complete rollout by late June.

We will begin rolling out in mid-June and expect to complete rollout by late July (previously late June).

[When this will happen:]

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

[When this will happen:]

Rollout will begin in mid-July (previously late June) and is expected to be complete by late July (previously mid-July).

This message is specifically associated with Microsoft 365 Roadmap ID 95787

[When this will happen:]

Graph Beta We will begin rolling out in late July (previously early July) and expect to complete by early August (previously mid-July).

Standard Release: We will begin rollout in late August and expect to complete by mid-September.

This message is associated with Microsoft 365 Roadmap ID 85619

[When this will happen:]

Rollout to public preview began in mid-June and is expected to be complete by late July.

Standard release will begin in early August and is expected to be complete by late September.

This message is associated with Microsoft 365 Roadmap ID 85619

[When this will happen:]

Rollout to public preview began in mid-June and is expected to be complete by early September.

Standard release will begin in early September (previously early August) and is expected to be complete by late October (previously late September).

The Power Apps “Per User” SKU will be renamed to Power Apps “Premium per user.”

The Power Automate “Attended RPA per user” SKU will be renamed to Power Automate “Premium per user” and the price will be reduced from $40 per user/month to $15 per user/month.

The updated SKU names and reduced pricing will take effect August 1st, 2023, in the price list. There are no changes to the capabilities or service plans that are included in these SKUs.

How will this affect your organization:

If you are an existing customer of the Power Automate “Attended RPA per user” SKU, you will be eligible to take advantage of the new pricing on your renewal date. If you are an existing customer of the Power Apps “Per User” SKU, your SKU name will be automatically updated in your Microsoft Agreement on August 1st, 2023.

Please reach out to your Microsoft representative if you have additional questions.

The name change to Microsoft Entra ID represents the evolution and unification of the Microsoft Entra product family, and a commitment to simplify secure access experiences for everyone.

No changes to capabilities, licensing, or pricing

Features and capabilities of Azure AD will continue to be available in Microsoft Entra ID. Prices, terms, and service level agreements also remain the same. To make the transition seamless for you, the Azure AD URLs, APIs and authentication libraries are staying the same, as are developer experiences.

[When this will happen:]

The name change will roll out across all Microsoft products and experiences throughout the second half of 2023. Customers who have access to Azure AD will continue to have access without any planned disruptions.

Resources:

Learn more about the name change for Azure AD

Read the blog about the latest Microsoft Entra announcements

No action is required from you.

The name change to Microsoft Entra ID represents the evolution and unification of the Microsoft Entra product family, and a commitment to simplify secure access experiences for everyone.

No changes to capabilities, licensing, or pricing

Features and capabilities of Azure AD will continue to be available in Microsoft Entra ID. Prices, terms, and service level agreements also remain the same. To make the transition seamless for you, the Azure AD URLs, APIs and authentication libraries are staying the same, as are developer experiences.

Timing of name change

The name change will roll out across all Microsoft products and experiences throughout the second half of 2023. Customers who have access to Azure AD will continue to have access without any planned disruptions.

Resources:

Learn more about the name change for Azure AD

Read the blog about the latest Microsoft Entra announcements

This capability is available for public preview for all organizations (IBv1 (legacy) and IBv2 architecture).

[When this will happen:]

The capability is available now for public preview to all organizations.

This capability is available for public preview for all organizations (IBv1 (legacy) and IBv2 architecture).

[When this will happen:]

The capability is available now for public preview to all organizations.

4. In-chat search will now also be available in pop-out chats.

https://www.microsoft.com/microsoft-365/roadmap?rtc=1&searchterms=98121&filters=&searchterms=122550

Intune What's new 2306(June) Blog

Staying up to date on Intune new features, service changes, and service health

https://aka.ms/intunewhatsnewtoday

https://aka.ms/MEMServiceChangeBlog

https://techcommunity.microsoft.com/t5/intune-customer-success/microsoft-intune-service-updates/ba-p/358728

Intune In development

For organizations with users around the globe, we recognize that "outside of normal business hours" might affect you differently. We apologize for the impact this may have on your users. We are working hard to improve Viva Goals, to minimize these maintenance windows.