Microsoft Roadmap, messagecenter en blogs updates van 03-10-2024

Updated October 2, 2024: We have updated the rollout timeline below. Thank you for your patience.

Before this rollout, users can indicate in Microsoft Teams if they are in office or remote by manually setting their location by selecting their profile photo at the top right of Teams. With this rollout, we are introducing automatic location updates on bookable desks to make it easier for users to keep their work location up to date and connect with others in the office.

In addition to this feature rolling out to bookable desks, it will also be rolling out to BYOD rooms.

This message is associated with Microsoft 365 Roadmap ID 401118.

[When this will happen:]

General availability (Worldwide) for bookable desks: We will begin rolling out mid-September 2024 (previously early September) and expect to complete by late September 2024 (previously mid-September).

General availability (Worldwide) for BYOD rooms: We will begin rolling out late October 2024 and expect to complete by early November 2024.

[How this will affect your organization:]

Bookable desks refer to unassigned seats in the office that are equipped with devices such as monitors or other peripherals. Admins can associate these devices to a workspace account using the Teams Rooms Pro Management portal. This association will allow users to automatically claim a desk, and (in future) will provide IT with valuable usage analytics and reports. Learn more: Setting up Bookable Desks in Microsoft Teams – Microsoft Teams | Microsoft Learn. After configuring bookable desks, admins can enable automatic location updates at the tenant level or for a specific user group. Then, users can enable the feature at Teams > Settings (three-dot menu in top right of the screen) > Privacy > Sharing your work location. After users enable the feature, their work location will automatically update to In the office when they connect to a bookable desk, if their location was previously set to Unknown or Remote.

To help users find this feature, after an admin enables the feature, the banner “Looks like you’re in the office” will appear the first time a user plugs into a bookable desk.

After a user enables automatic location updates, the banner “You’re connected to your organization’s network or device” will appear once when they plug into a bookable desk. The banner confirms that the user has successfully enabled automatic location update.

[What you need to do to prepare:]

This rollout will happen automatically by the specified date with no admin action required before the rollout. To prepare for this feature, we recommend communicating this new feature to your users and admin team and sharing instructions if needed. After this feature rolls out, admins can enable automatic location updates at a tenant level or for a specific user group. Then, users can enable automatic location detection in Teams Settings > Privacy as described earlier.

Updated October 2, 2024: After further review we have decided not to proceed with this change at this time. We apologize for any inconvenience.

We are updating the way multiple images within a chat can be viewed.

[When this will happen:]

We will begin rolling this out in mid-September 2024 and expect to complete by mid-October 2024 – We will not be proceeding with this change at this time.

[How this affects your organization:]

When there are multiple images within a chat, users will now be able to view and cycle through the images. The images are deep linked to take the user to the specific time in the chat the image was provided.

[What you can do to prepare:]

The feature will be available by default. There is no specific action needed, but you may consider updating your training and documentation as appropriate.

Updated October 2, 2024: We have updated the rollout timeline below. Thank you for your patience.

Coming soon for Microsoft Outlook for iOS and Android: Online archive mailboxes is a feature that offers users advanced archiving capabilities in the Mailbox archive. An Outlook online archive mailbox can store older email messages where they won’t occupy space in the user’s primary mailbox. This specialized mailbox appears with your other mailbox folders in Outlook. After this rollout, if you have enabled Mailbox archive for your users, the Online Archive mailbox will appear in the folder list, which users can access by tapping their profile in the top left of their screen.

NOTE: The Online Archive folder is different than the Archive folder. Using the Archive button to move messages to the Archive folder doesn’t reduce your mailbox size. Learn more about the Archive folder: Archive in Outlook for Windows – Microsoft Support.

Before this rollout, users are only able to access their online archive emails in Outlook for iOS and Android through Search. After this rollout, users will be also able to access archived email in the Online Archive folder.

Learn more about the admin policy: Enable archive mailboxes for Microsoft 365 | Microsoft Learn

Learn more about the user experience: Manage email storage with online archive mailboxes – Microsoft Support (will be updated soon)

[When this will happen:]

General Availability | Outlook for iOS (Worldwide GCC, GCC High, DoD): We began rolling out mid-August 2024 and expect to complete by late October 2024.

General Availability | Outlook for Android: We will begin rolling out early October 2024 (previously late September) and expect to complete by late October 2024. 

[How this will affect your organization:]

For tenants where admins have enabled Mailbox archive for users in the Exchange admin center, users will start seeing Online Archive in their folder list in Outlook mobile.

If admins do not turn on Mailbox archive for a user, this feature is disabled. Learn more in the section called How to enable an archive mailbox in Enable archive mailboxes for Microsoft 365 | Microsoft Learn.

[What you need to do to prepare:]

This rollout will happen automatically. You may want to notify your users about their archives appearing in the folder list and update any relevant documentation.

Microsoft Places, an AI-powered workplace app for flexible work, will be generally available in Q4 CY24. Places reimagines flexible work with AI by intelligently coordinating your hybrid team to make the most of in-office days, modernizing how employees connect, and optimizing space management with occupancy and utilization data.  

There will be two new service plans for core and premium features:

• Places core (PLACES_CORE)
• Places enhanced (Microsoft Places premium) (PLACES_ENHANCED)

As an existing customer, you will see an additional service plan as part of your Office 365 subscription: Places core. This service plan includes all core features such as setting up and updating location plans, viewing collaborators’ location plans, accessing peek card experiences, scheduling in person meetings, managing hybrid RSVP, and workplace presence related capabilities.

If you have Teams Premium, you will have Places enhanced premium features like Places Finder, intelligent booking, Places Explorer, Places Space Analytics, and auto-release policies.   

We will be backfilling these service plans into the following SKUs below.

List of SKUs for Places core: 

• Microsoft 365 Business Basic 
  
• Microsoft 365 Business Standard 
  
• Microsoft 365 Business Premium 
  
• Microsoft 365 or Office 365 E1, E3, E5 
  
• Microsoft 365 or Office 365 F3 
  

List of SKUs for additional Teams-specific features in Places core: 

• Microsoft Teams Essentials 
  
• Microsoft Teams Enterprise 
  
• Microsoft Teams EEA 
  

List of SKUs for Places enhanced: 

• Microsoft Teams Premium Introductory Pricing

We will begin rolling out both service plans in mid- to late-November for all platforms. Once the Places core service plan is deployed to your organization, core features will become available within your Office 365 subscription with basic set up and onboarding buildings to Places directory. Enhanced experiences will require additional deployment planning.     

Learn about Microsoft Places and the value that Places delivers for flexible work. Participate in our public preview and begin conversations with your IT Admin, relevant BDMs (RE&F) and leadership teams to understand how they are implementing hybrid work policies and managing occupancy & utilization challenges today. Start to gather workplace locations, existing floor plans, etc. to get ready for onboarding plans.

Learn more:

• Microsoft Places 
• Microsoft Places: Using AI for flexible work | Microsoft 365 Blog 
  
• Microsoft Places overview – Microsoft 365 Places | Microsoft Learn 
  
• Deployment guide for Places – Microsoft 365 Places | Microsoft Learn

As mentioned in MC726113/MC674247, Google has deprecated Android device administrator management, continues to remove management capabilities, and no longer provides fixes or improvements. Due to these changes, Intune will be ending support for Android device administrator management on devices with access to Google Mobile Services (GMS) beginning December 31, 2024. Until that time, we will support device administrator management on devices running Android 14 and earlier. For more details, read the blog: https://aka.ms/Intune-Android-DA-blog.

[How this will affect your organization:]

After Intune ends support for Android device administrator, devices with access to GMS will be impacted in the following ways:

1. Users will not be able to enroll devices with Android device administrator.
2. Intune will not make changes or updates to Android device administrator management, such as bug fixes, security fixes, or fixes to address changes in new Android versions.
3. Intune technical support will no longer support these devices.

[What you need to do to prepare:]

Stop enrolling devices into Android device administrator and migrate impacted devices to other management methods. You can check your Intune reporting to see which devices or users may be affected. Go to Devices > All devices and filter the OS column to Android (device administrator) to see the list of devices.

Read the blog, Microsoft Intune ending support for Android device administrator on devices with GMS in December 2024, for our recommended alternative Android device management methods and information about the impact to devices without access to GMS.

This is a reminder that we are retiring Microsoft Delve on December 16, 2024, as communicated in MC698136 (Updated) Retiring Delve Web (originally published December 2023, updated May 2024).

In addition to the details in MC698136, learn more at:

• Alternatives to Delve in Microsoft 365 – Microsoft Support
• Guidance for retiring Delve in your organization

Please review these sources and update your internal documentation and training.

We’re contacting you because your tenant uses legacy Exchange Online tokens that are deprecated and Outlook add-ins that still use them will break when tokens are turned off.

• Legacy Exchange Online user identity tokens and callback tokens are deprecated and will soon be turned off for all Exchange Online tenants. This is part of Microsoft’s Secure Future Initiative to protect orgs in the current threat landscape. If add-ins use legacy tokens to make calls to Exchange, developers need to migrate from Exchange tokens to using Nested App Authentication (NAA) and Entra ID tokens ASAP.
• Code changes to add-ins using legacy Exchange Online tokens are required to ensure they continue to work. We recommend you update affected add-ins to use NAA, which provides simple authentication and top tier identity protection through APIs designed specifically for add-ins in Office hosts.

NOTE: This change only applies to Exchange Online; add-ins used in on-premises environments are not impacted by this change.

[Recommended actions:]

• Administrators: Identify which add-ins need to be updated and contact the ISVs or developers of those applications to get updates.
• Developers: Check the add-in code to see if the related API calls are used and then make appropriate updates.
• Register: The updated add-ins require an application registration in Microsoft Azure. Developers need to create an application registration for each add-in. Admins need to consent to the application registration for each add-in’s required permissions.
• Don’t wait: Add-ins are often part of mission critical functions, and the updates will take time to implement. It’s best to implement updates well before legacy Exchange Online tokens are turned off.

[When will Microsoft turn off legacy Exchange Online tokens?]

The following table lists the key milestones based on which Office app release channel tenant you’re using. Note that the GA date for NAA varies based on channel. We’ll soon provide tooling via PowerShell for Microsoft 365 administrators to reenable legacy Exchange tokens for their tenant or specific add-ins if those add-ins are not yet migrated to NAA.

NAA availability for Outlook on Mac, Android, iOS, new Outlook, and Outlook on the web will align with the Microsoft 365 Current Channel release. Support for Work and School accounts as well as Microsoft account will be available for Classic Outlook on Windows, Outlook on Mac, Android, and iOS at GA. Work and School accounts will be supported on new Outlook and Outlook on the web at GA, with Microsoft account support shortly thereafter.

Note: If a single tenant uses multiple Microsoft 365 apps / Office release channels, Legacy Exchange Online tokens will be turned off based on the “slowest” release channel.

[How do I check which Outlook add-ins are impacted?]

Add-ins may use the legacy Exchange tokens to get resources from Exchange through the EWS or Outlook REST APIs. Sometimes an add-in requires Exchange resources for some use cases and not others, making it difficult to figure out whether the add-in requires an update. We recommend reaching out to add-in developers and owners to ask them if their add-in code references the following APIs:

• makeEwsRequestAsync
• getUserIdentityTokenAsync
• getCallbackTokenAsync

We’ll provide tooling via PowerShell for Microsoft 365 admins in October 2024 to turn legacy Exchange tokens on or off in your tenant. This will allow you to test if any add-ins are using Exchange tokens. We’ll provide more info when the tooling is ready in the Outlook legacy token deprecation FAQ.

If you rely on an independent software vendor (ISV) for your add-in, we recommend you contact them as soon as possible to confirm they have a plan and a timeline for moving off legacy Exchange tokens. ISV developers should reach out directly to their Microsoft contacts with questions to ensure they’re ready for the end of Exchange legacy tokens. If you rely on a developer within your organization, we recommend you ask them to review the Updates on deprecating legacy Exchange Online tokens for Outlook add-ins blog and ask any questions to the Outlook extensibility PM team on the OfficeDev/office-js GitHub issues site.

[How do I keep up with the latest guidance?]

We’ll share additional guidance on the Office Add-ins community call, the M365 developer blog, and the Outlook legacy token deprecation FAQ.

Ask questions about NAA and legacy Exchange Online token deprecation on the OfficeDev/office-js GitHub issues site. Please put “NAA” in the title.

Additional resources:

• NAA public preview blog
• Microsoft 365 developer blog: Updates on deprecating legacy Exchange Online tokens for Outlook add-ins
• NAA docs to get started
• NAA FAQ
• NAA Outlook sample
• NAA WXP sample