I can't believe I've had to spend time out of my day to put in place countermeasures and automated removal of what is certainly going to be a dumpster fire of an idea. This is absurd.
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
THIS! I just had to spend 30 minutes downloading the new ADMX templates, copying them up to our forests and deploying a new GPO in all of them just to block this. This is insanity.
Make matters worse, on our tenant we can't even see any of the policies in Intune to prevent this forced deployment... Administrative Template doesn't have "Don't install extension for Microsoft Search in Bing that makes Bing the default the search engine". But if you're on legacy internal domain you can copy the ADMX template to get the required GPO configured. Also within Intune, there's no option to Exclude Bing within Configure App Suite! Guess you have to manually import your XML like the early Intune days to make sure it's not included in your app push. Really need all areas covered, they missed the boat on modern management! I'm thinking maybe the Admin Template can be somehow manually deployed through ADMX ingestion. Either way, it's a headache to come up with the countermeasures on modern management, wayyyy too much overhead!
@jleger88 You definitely have me beat on the scope of what it is going to take to prevent or remove this.
Based on customer feedback, we're making a few changes to the plan to roll out the extension for Microsoft Search in Bing. For information about the changes, read this announcement. This article will be updated when more details are available.
Most helpful comment
THIS! I just had to spend 30 minutes downloading the new ADMX templates, copying them up to our forests and deploying a new GPO in all of them just to block this. This is insanity.