![Microsoft Teams admin center: “WatermarkWithDisplayNameAndIP” retires in October 2024 from Teams meeting policy [MC899939]](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-pachon-in-motion-426015731-16727556-1024x683.webp)
We will retire the Microsoft PowerShell command value WatermarkWithDisplayNameAndIP for WatermarkForAnonymousUsers for the Microsoft Teams meeting policy on October 27, 2024. We will continue to support the values WatermarkWithDisplayName (the default value) and JoinWithAudioOnly.
[How this will affect your organization:]
You are receiving this message because our reporting indicates your organization may be using the WatermarkWithDisplayNameAndIP value for WatermarkForAnonymousUsers in your Teams meeting policy settings.
Admins will receive an error if they attempt to use WatermarkWithDisplayNameAndIP after this change is implemented.
[What you need to do to prepare:]
This change will happen automatically by the specified date. No admin action is required. Please notify your admins of this change and update relevant documentation.
Learn more: PowerShell Gallery | MicrosoftTeams 6.5.0 (will be updated before the policy retires)
Source: Microsoft
![Microsoft 365 Copilot: Self-service purchase settings in Microsoft 365 admin center (E3, E5) [MC899941]](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-pachon-in-motion-426015731-18204592-150x150.webp)
![Product transitions to the cloud.microsoft domain – September 2024 [MC901821]](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-rquiros-2330137-150x150.webp)
The retirement of the “WatermarkWithDisplayNameAndIP” feature from the Microsoft Teams meeting policy in October 2024 might make some admins and users do a double-take!
For admins, this change means they’ll need to bid farewell to using “WatermarkWithDisplayNameAndIP” and switch to either “WatermarkWithDisplayName” or “JoinWithAudioOnly.” So, if an admin tries to sneak in the old command after the retirement date, they might get an error message that says, “Oops, that feature has left the chat!”
As for users, they might not notice much of a difference directly, but behind the scenes, admins will be doing a little dance to ensure everything runs smoothly without the retired feature. It’s like backstage magic at a concert – the show goes on flawlessly, but there’s a lot happening behind the curtains! ✨
In terms of criticality, this change is like switching from a fancy fountain pen to a trusty ballpoint pen – it might take a bit of adjustment, but in the end, the writing still gets done! So, it’s important for admins to be aware of the change, update their documentation, and inform their teams, but it’s not a show-stopping crisis. Just a little tech tango to keep things moving smoothly!
Remember, change is the only constant in the tech world, so let’s embrace this update with open arms!