Deprecating "Turn On File Synchronization Via SOAP Over HTTP" Group Policy setting
What is changing? We are removing the âTurn on file synchronization via SOAP Over HTTPâ policy from Group Policy. This policy allows IT admins to turn file synchronization via SOAP over HTTP on or off for Office. Before policy was removed File Synchronization via SOAP over HTTP can be turned on or off by Admins via policy or by users via adding the FSSHTTPOff registry key to HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\1x.0\Common\Internet. After policy is removed It will not be possible to turn file synchronization via SOAP over HTTP on or off via Group Policy setting or by adding the FSSHTTPOff registry key. Office will always use SOAP as its preferred protocol to open documents on SharePoint. Why is it changing? This policy was originally introduced when Office switched to using SOAP protocol to connect and exchange information with newer versions of SharePoint. This policy was implemented to give admins better control of this transition, particularly for older versions of SharePoint 2013 on-premises deployments. As this transition completed, weâve found that some users turn this policy off in an attempt to troubleshoot "Sorry we can't open https://" or "Upload failed." error messages when trying to open documents on a SharePoint website. Setting the policy to Disabled adds the FSSHTTPOff registry key and it prevents Office from using its preferred protocol to open documents on SharePoint. It also prevents features such as co-authoring, checking documents in and out, reverting to earlier versions of documents, filling out required file properties, and so on, to function properly. As a result, we are retiring this policy in favor of always using SOAP as the preferred protocol for Office to open documents on SharePoint. When is it changing? This change is rolling out starting with Version 2208. Version 2208 is expected to be available in Current Channel in late August 2022, and in Semi-Annual Enterprise Channel in January 2023. Even though the policy will continue to appear for a bit longer in Group Policy tools, if youâre using Version 2208 (Build 16.0.15601. 10000 ) or later, the policy and the registry key will not have any effect. (Office LTSC 2021, Office 2019, Office 2016, and Office 2013 will continue to honor the policy). If you or your organization is affected by the removal of this policy, please let us know about your scenario by emailing: FileSyncViaSOAP@microsoft.com Related Articles https://support.microsoft.com/en-us/office/using-the-fsshttpoff-registry-key-fd193fa2-9b23-4e60-8527-1bf760b2d470 https://docs.microsoft.com/en-us/openspecs/sharepoint_protocols/ms-fsshttp/05fa7efd-48ed-48d5-8d85-77995e17cc81?redirectedfrom=MSDN
Office 365 2013 and Win1 License messages
We are using Office 365 with 2013 Office products. When we open any Office product on SOME terminals running Win11, we get a message that the license is not active, but everything works fine after acknowledging the error. People still running Win10 work fine. Even some on Win11 work fine, but after doing a Registry edit. Had a couple where the registry edit didn't work and still get the messages.
Effects of editing Organization profile
The company I work for are considering editing the company name in the Microsoft 365 administration centre, as described in https://docs.microsoft.com/en-us/microsoft-365/admin/manage/change-address-contact-and-more?view=o365-worldwide I am aware that this can trigger a need for users to re-syncronize their OneDrive in File Explorer. Apart from this, the other effects described in the article I linked to above, is desired effects for the company. However, we are looking into whether editing the company name could trigger any unforeseen and unwanted side effects. As an example, the tenant has some third party software currently using Azure AD for access rights. Looking for any experience anyone have had editing the company name, and whether there are any effects that could complicate use of the tenant, and/or confirmation that this is only affecting the elements described in the article.
Alert Policy for Mail.IsThreat
I want to be able to trigger an Alert Policy in the event of an inbound message being detected as a Mail Threat. I have created an New-ProtectionAlert object with the following -filter parameter -Filter "(Mail.IsThreat -eq 1) -and (Mail.Direction -eq 'Inbound')" The inbound message will be passed to a custom connector I have written, which will perform some policy checks and then return the message to Office365. If the policy is violated, I would like to add a property? message header? something else? that will set the Mail.IsThreat property to 1 and hence trigger the alert. I'm struggling to see how/where the Mail.IsThreat is defined or if it can be defined outside of the standard M365 Threat Protection features
Group Calendar for a Rural Clinic?
Hi. I'm helping a Rural Clinic re-think how they're sharing executive calendars with Board Members. Example, they keep notes in a spreadsheet about their annual financial calendar - you might be able to imagine the issues. Within Outlook, or MS Groupware - what suggestions would you make about how to leverage Office to work with employees on the domain as well as with a flux of resources that sit outside? Thanks!Microsoft massaging center
Hi everyone, we use Cloud O365 and there is something related to security, where we have the cloud update without even our acceptation and we follow Microsoft massaging center just to be updated about the changes that Microsoft makes but we don't have the control for these kind of things. For example See the massage that they sent for Microsoft to do update. "In MC215678 (June 2020), we announced that Microsoft To Do would support list sharing between personal Microsoft accounts and work or school accounts. We paused the rollout to incorporate your feedback. We are pleased to announce we are moving forward with this feature. Once available, this feature will be enabled by default if you have not customized the setting for your tenant." As a security perspective sharing personal account with work account is not recommended and most of companies will not turn that on. They don't even classify their updates (regular update, emergency update, new feature ...ext.) my question is what should i do?, is there any policy that could control these kind of things or should we have a written policy or procedure for it? Thanks
Alerts to Key workers
As part of the disaster scenario solutions for the organisation we have a system called Everbridge that allows the emergency response team to send out SMS texts, emails and Everbridge app messages to staff (currently 288 work mobiles) when there is an issue with the building or the network access. Can you think of any element within O365 that could do something similar if all work phones had O365 element installed?
