awesome-dotnet-core VS Dynamics-365-Workflow-Tools

Regarding your reservations:

1. Microsoft is a pretty big contributor to Linux at this point. Their cloud arm pretty much forced their hand and I don't see that story changing anytime soon. .NET on Linux has been great in my experience.

2. Some libs are, others are decidedly _not_ enterprise driven. The ecosystem is pretty large so there tends to be a lot of options with most packages. Just take a look here, https://github.com/thangchung/awesome-dotnet-core, the ORM section has things as big as nhibernate, which is about as heavy-handed as it gets, to things like Dapper which is about as lightweight as you can get.

You can find interesting packages/projects for searching "awesome dotnet" in github. For example: https://github.com/quozd/awesome-dotnet https://github.com/thangchung/awesome-dotnet-core

For example the https://github.com/thangchung/awesome-dotnet-core Sample Projects section.

Awesome .NET Core

Another huge resource for .Net Core is https://github.com/thangchung/awesome-dotnet-core

As a very similar alternative to above, but without the need for a new field, you could install Dynamics 365 Workflow Tools (https://github.com/demianrasko/Dynamics-365-Workflow-Tools) and use the ismemberofteam workflow step (https://github.com/demianrasko/Dynamics-365-Workflow-Tools/blob/master/docs/IsMemberOfTeam.md) to check if the modified by user is in the back office team.

You could use Dynamics-365-Workflow-Tools within a real time workflow use the Rollup Functions method to count the number of activities regarding to the lead an throw an error with a custom message via stopping the workflow when the count is less than 1.

The logic below would work using share / unshare if you install Demian Ruskos workflow tools (https://github.com/demianrasko/Dynamics-365-Workflow-Tools) or with out of the box assign / unnasign if you get your business units working.