Microsoft Learn is a new platform for cloud training

microsoft-learn

Recently Microsoft announced their new platform to get the basic level of understanding for some cloud technologies and products like Azure, PowerApps, Flow, etc. It is interesting that it’s not just a set of modules but they are combined into learning paths with gamification where users could earn points, badges, etc.

Introducing Microsoft.com/Learn

SharePoint workflows stop working after you install .NET security updates for CVE-2018-8421

Symptoms


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.

Cause


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.

Resolution

The official KB is here and MSFT blog post is here

3 reasons we have switched from Slack to Microsoft Teams

slack-to-teams.jpg

Back in 2017, Microsoft announced their strategy to make Microsoft Teams be a single platform for communications as part of Office 365 suite. I’ve tried using Teams since Beta release, but it was too early at least for us to use it in real life and Slack was much better, so we’ve decided not to make any migrations there.

Recently, I was rechecking Teams, and we decided to make a migration from Slack, and I’ll share my top 3 reasons why

  1. We are using Office 365, so we don’t need to pay extra for Teams licenses, and that’s why we are getting some benefits comparing to free Slack plan
    • Unlimited access to old messages
    • An infinite number of integrations with 3rd party services
    • Guest users support
    • Group calls
  2. Single user directory which is an Azure AD, so we don’t need to manage users in multiple places
  3. An easy way to build a knowledge base in the scope of a team and I’m talking about both Files and Wiki here which is possible due to tight SharePoint integration

For the last couple years, we were using Skype, HipChat (RIP), Slack and now it’s Microsoft Teams. For now, Teams seems to be the most comfortable product for us, and I like to see the progress Product Group is making to make it even better. Feel free to review Office 365 Roadmap.

3 причины почему мы перешли на Microsoft Teams из Slack

slack-to-teams.jpg

Еще в 2017 Microsoft презентовали свою стратегию, в рамках которой планировалось сделать Microsoft Teams флагманским продуктом для коммуникаций вместо Skype for Business. Лично я пробовал Teams еще со времен Beta релиза, но тогда это был очень сырой продукт, и Slack на его уровне выглядел сильно лучше.

Не так давно мы полностью переехали в Teams из Slack, и вот почему

  1. Мы уже пользуемся Office 365, и значит Teams уже включен в подписку и за него не нужно дополнительно платить. Отсюда получаем ряд преимуществ по сравнению с бесплатным планом Slack
    • Неограниченный доступ к старым сообщениям
    • Бесконечное количество интеграций со сторонними сервисами
    • Работа с внешними пользователями
    • Групповые звонки
  2. Единый каталог пользователей – в нашем случае Azure AD
  3. Способ собрать базу знаний по проекту в одном месте – речь про вкладки с документами и вики, что реализовано за счет интеграции с SharePoint

За последние несколько лет мы внедряли и ежедневно пользовались Skype, HipChat (RIP), Slack и сейчас это Microsoft Teams. Из всех продуктов Teams для нас выглядит самым удобным продуктом и особенно радует, что продуктовая команда постоянно работает над улучшениями, список которых можно найти в Office 365 Roadmap.

Устаревшие и удаленные функции SharePoint Server Preview 2019

sharepoint-2019

Новая версия SharePoint изменяет набор функциоанала, например что-то объявили устаревшим, а что-то отключили. Разница в этих двух категориях заключается в том, что устаревшими функциями можно пользоваться в текущей версии, в следующей версии их уже не будет.

Continue reading