In this blog we show you how to create a build and a release pipeline in Azure DevOps that use one parameterized task group for deploying Azure Logic Apps and Functions to different environments.
The Microsoft Dynamics CRM 2013 and Microsoft SharePoint 2010/2013 integration remains much as it was in CRM 2011 and is designated as not being a refreshed entity. However, there is a nice improvement in the document location and folder name.
The setup is exactly the same in CRM 2013 as it was in CRM 2011, which you can reference here.
Here is a summary of the setup for a new CRM 2013 deployment:
Now for the cool new part. The folder name is no longer simply the account record name—the CRM record's GUID is appended to the folder! You can see that the CRM document location record displays the folder name.
Navigate to SharePoint and see the corresponding folder.
This improvement in the CRM 2013 and SharePoint integration simplifies additional development. It should also should expedite further integration between the two applications, because now SharePoint knows the unique ID of the CRM record!