MC391951 – Updated November 2, 2022: Microsoft has updated the rollout timeline below. Thank you for your patience.
The ability to search online images through Bing is coming soon to Whiteboard web, Teams and Windows App.
This message is associated with Microsoft 365 Roadmap ID 93341
When this will happen:
Microsoft will begin rolling out in mid-September and expect to complete rollout by late November (previously late October).
How this will affect your organization:
This service can be controlled by optional connected experiences policy, which controls whether users have access to the functionality. Today this policy only applies to the ability to see a link in Whiteboard where users can provide feedback using Microsoft’s Feedback portal.
What you need to do to prepare:
No change is necessary, unless you wish to disable the Bing Image Search functionality (and other optional connected experiences) in Whiteboard. To do this, you can use the Office cloud policy service in the Microsoft 365 Apps admin center.
- Sign in to https://config.office.com/ with your Microsoft 365 admin credentials
- Select Customization from the left pane.
- Select Policy Management
- Create a new policy configuration or edit an existing one.
- In Choose the scope, choose the security group for which you want to apply the policy.
- In Configure Settings, choose Allow the use of additional optional connected experiences in Office.
- In configuration setting, choose either – enabled, disabled, or not configured. The implication of each of these options is mentioned below:
- Enabled: Optional connected experiences are available to users
- Disabled: Optional connected experiences aren’t available to users
- Not configured: Optional connected experiences are available to users
- Save the policy configuration.
- Reassign priority for any security group if required. (If two or more policy configurations are applicable to the same set of users, the one with the higher priority is applied)
- In case you create a new policy configuration or change the configuration for an existing policy, there will be a delay in the change being reflected as mentioned below:
- -> If there were existing policy configurations prior to the change, then it will take 90 mins for the change to be reflected
- -> If there were no policy configurations prior to the change, then it will take 24 hours for the change to be reflected
Additional information