In short, SharePoint 2010 workflows in Office 365 are retired. The only supported way to create automation is Microsoft Power Automate (ex. Microsoft Flow).
| Date | Action |
|---|---|
| August 1, 2020 | SharePoint 2010 workflows will be turned off for any newly created tenants. |
| November 1, 2020 | SharePoint 2010 workflow services will be removed from existing tenants. |
More details can be found here.
The minimum supported patch level for the SharePoint 2013/2016 was updated:
Recently, one of my clients reported an issue where they were not able to access their SharePoint 2010 on Windows Server 2008 R2. It was really interesting that only some users were affected and it’s turned out that it wasn’t working just for local members of local “Administrators” group.
In short, there was an issue with a Microsoft update KB4480970 released on January 8, 2019 and then 3 days later Microsoft release a fix for it KB4487345.
After any of the September 2018 .NET Framework security updates to resolve CVE-2018-8421 (.NET Framework Remote Code Execution Vulnerability) are applied, SharePoint out-of-the-box workflows stop working. When the problem occurs, an error that resembles the following is logged:
<Date> <Time> w3wp.exe (0x1868) 0x22FC SharePoint Foundation Workflow Infrastructure 72fsUnexpected RunWorkflow: Microsoft.SharePoint.SPException: <Error><CompilerError Line="-1" Column="-1" Text="Type System.CodeDom.CodeBinaryOperatorExpression is not marked as authorized in the application configuration file." /><CompilerError Line="-1" Column="-1" Text="Type System.CodeDom.CodeBinaryOperatorExpression is not marked as authorized in the application configuration file." /><CompilerError Line="-1" Column="-1" Text="Type System.CodeDom.CodeBinaryOperatorExpression is not marked as authorized in the application configuration file." /><CompilerError Line="-1" Column="-1" Text="Type System.CodeDom.CodeBinaryOperatorExpression is not marked as authorized in the application configuration file." /><CompilerError Line="-1" Column="-1" Text="Type System.CodeDom.CodeBinaryOperatorExpression is not marked as authorized in the application configuration file." /><CompilerError Line="-1" Column="-1" Text="Type System.CodeDom.CodeBinaryOperatorExpression is not marked as authorized in the application configuration file." /><CompilerError Line="-1" Column="-1" Text="Type System.CodeDom.CodeBinaryOperatorExpression is not marked as authorized in the application configuration file." /><CompilerError Line="-1" Column="-1"…
The error suggests that System.CodeDom.CodeBinaryOperatorExpression is not included in the authorized types.
For more information about the September .NET Security updates, go to this Microsoft blog page.
Workflow Foundation (WF) will only run workflows when all dependent types and assemblies are authorized in the .NET config file (or added explicitly through code) under the following tree:
<configuration>
<System.Workflow.ComponentModel.WorkflowCompiler>
<authorizedTypes>
<targetFx>
However, after the update, some types that are used by SharePoint out-of-box workflows that were not previously required are now required.
Product group released Cumulative Update and it is available for download.
Direct link to download updates Continue reading
Product group released Cumulative Update and it is available for download.
Direct link to download updates
Note: Install both fixes to fully patch a SharePoint server.
Please run SharePoint 2016 Products Configuration Wizard on every server on the farm.
You could use the SharePoint Server 2016 Patch Build Numbers Powershell Module to identify the patch level of all SharePoint components.
Новый накопительный пакет обновлений для SharePoint 2016 доступен для загрузки
Прямая ссылка для загрузки обновлений
Важно! Необходимо установить оба исправления для полного исправления сервера SharePoint.
После установки обновлений не забудьте запустить SharePoint Configuration Wizard на каждом сервере фермы.
Чтобы определить уровень патча для всех компонентов SharePoint, Вы можете использовать SharePoint Server 2016 Patch Build Numbers Powershell Module.
Microsoft MVP & Office 365 Consultant Blog 