{"id":11125,"date":"2017-06-16T12:22:44","date_gmt":"2017-06-16T19:22:44","guid":{"rendered":"https:\/\/www.microsoft.com\/insidetrack\/blog\/?p=11125"},"modified":"2023-06-16T16:04:11","modified_gmt":"2023-06-16T23:04:11","slug":"beyond-crm-extending-dynamics-365-to-manage-contracts","status":"publish","type":"post","link":"https:\/\/www.microsoft.com\/insidetrack\/blog\/beyond-crm-extending-dynamics-365-to-manage-contracts\/","title":{"rendered":"Beyond CRM: Extending Dynamics 365 to manage contracts"},"content":{"rendered":"
This content has been archived, and while it was correct at time of publication, it may no longer be accurate or reflect the current situation at Microsoft.<\/p>\n<\/div>\n<\/div>\n
When managing advertising agreements became complex and error-prone, Microsoft Digital turned to Microsoft Dynamics 365 to create a contract life cycle solution. The system streamlined contract creation, approval, and management\u2014and moved Dynamics 365 beyond customer relationship management. It integrates with external systems like SAP and DocuSign to automate, digitize, and simplify contracts and transactions. The system set the standard for hybrid cloud configurations at Microsoft.<\/p>\n
Managing advertising operations\u2014specifically, selling or buying ad space\u2014became unwieldy at Microsoft. Complex, nonstandard advertising agreements resulted in a manual, inconsistent, and highly segmented system that was sometimes prone to errors. The Advertising Operations team needed a consolidated system to streamline and manage online advertising agreements, end-to-end, so they approached Microsoft Digital for a new solution.<\/p>\n
Our Agreement Management Tool (AMT) has evolved into a cloud-based managed service that uses Microsoft\u00a0Dynamics 365 to push the limits of what customer relationship management (CRM) can be. AMT started as an on-premises, customized version of Dynamics CRM that improved our advertising contracts system. Today, AMT delivers a global, cloud-based, feature-rich system that manages the entire life cycle of online advertising agreements by automating, digitizing, and simplifying processes. AMT is a pioneering example of how we extended CRM to manage not just relationships\u2014but contracts and transactions too\u2014and it set the standard for hybrid cloud configuration systems at Microsoft.<\/p>\n
Managing advertising operations is complex. Contracts for buying, publishing, and managing advertising incentives and partnerships all have their own rules and come with their own sets of obligations. Microsoft sells advertising space on its own websites, like MSN.com. They also buy advertising space on other companies\u2019 websites. It\u2019s a big business\u2014they recognize hundreds of millions of dollars from advertising.<\/p>\n
Advertising agreements are nuanced, often non-standard, and they contain unique negotiated terms\u2014like revenue incentives. As Microsoft grew, Advertising Operations had to coordinate across multiple systems and tools. For example, to process an end-of-year payment, staff had to:<\/p>\n
It was hard to consistently apply business rules across multiple tools and processes. And analyzing data across multiple repositories was challenging.<\/p>\n
As you can imagine, navigating though complex and disjointed processes needed deep institutional knowledge. The system was labor intensive and exposed opportunities for error. Something as simple as searching for a contract meant emailing the Advertising Operations team and then pulling the data. And end-of-contract financial obligations were sometimes affected by contract unavailability, data extraction issues, or data entry errors.<\/p>\n
As the business grew, using separate tools such as Excel and Outlook made it difficult\u2014and sometimes impossible\u2014to enforce business rules, track processes, and analyze data. The original, internally developed system was highly customized, which made it both time- and resource-intensive.<\/p>\n
Ultimately, the need to reduce compliance risks triggered Advertising Operations ask us for a new solution that would give them a new level of control over how they manage contracts. The business needed a solution that used fewer tools, offered greater control, and had the ability to automate workflows.<\/p>\n
When we started investigating a new solution, we were immediately drawn to Microsoft Dynamics CRM. Dynamics\u00a0CRM can be configured rapidly, and it integrates easily with other applications. An on-premises instance of Dynamics\u00a0CRM was quickly created by an external IT partner, which improved the contract-creation system.<\/p>\n
As our knowledge of Dynamics 365 capabilities matured, we recognized the opportunity for a much more sophisticated system. We knew that Dynamics 365 would improve the advertising contract process by:<\/p>\n
AMT manages the end-to-end life cycle\u2014creation, approval, and management\u2014of online advertising agreements, plus the transactions associated with them.\u00a0AMT extends Dynamics CRM in unique and new ways. CRM systems are typically used to manage and analyze customer interactions and data throughout the customer life cycle, with the goal of improving business relationships, retaining customers, and driving sales growth. When we developed AMT, we adapted Dynamics CRM to:<\/p>\n
AMT effectively digitized the creation and management of advertising contracts. Here\u2019s an example, using the old contract signature workflow:<\/p>\n
Today, AMT with integrated DocuSign eliminates these steps and digitizes every aspect of the transaction. AMT distributes the draft to relevant parties, such as Microsoft Corporate, External, and Legal Affairs or Microsoft Finance, and manages those signatures. The AMT workflow brings the document back into Dynamics 365 and routes it into the signing repository.<\/p>\n
The team follows the same stages and steps for each customer interaction. AMT automatically sends emails, tracks responses, analyzes data, and manages other operations.<\/p>\n
When we were planning AMT, we knew that we wanted to take advantage of modern engineering principles that would get us to the cloud, fast. We envisioned an economical and efficient managed service model and a sprint delivery system, which would continuously deliver new functionality. We chose to configure out-of-the-box features\u2014rather than customizing code\u2014to economically and rapidly introduce new features.<\/p>\n
We used an Agile software development process, so that we could roll out technologies on an ongoing basis. We focused on business value, rather than features. Overall, we sought to build for the least amount of effort.<\/p>\n
Our continuous build, integrate, and deploy process used Visual Studio Team Services (VSTS), and we delivered to production in three-week sprint cycles consisting of:<\/p>\n
Sometimes, business issues extended our sprints by one week. But overall, we continuously deliver new features and quickly realize the benefits.<\/p>\n
AMT was envisioned and developed as a managed service.\u00a0<\/strong>A managed service is an outsourced IT function, where the service provider takes on proactive management responsibilities and tasks. It\u2019s a strategic way to improve operations and cut expenses.<\/p>\n AMT is based on modern engineering principles, such as DevOps, where development and operations roles merge, increasing efficiencies with maturity. In DevOps, the ideal is for any engineer to be able to do any task on the team. We used to separate our AMT team into infrastructure, development, test, and deployment roles. Now, it\u2019s a single feature group.<\/p>\n We incorporated unit test automation as part of the build process. The process automates repetitive but necessary tasks, and runs additional tests that would be difficult to do manually. Test automation is critical for continuous delivery and continuous testing, and is automated through VSTS. Deployment is also automated through VSTS.<\/p>\n Month over month, we deliver new features and gain benefits. We make very few changes to our processes to get the rewards. This changes the focus to reconfiguring existing features instead of customizing and creating new ones. Customizing code increases development and support costs, and potentially limits future upgrades. For example, we found that DocuSign customization requires additional management tasks during upgrades. As a rule, we avoid custom code at all costs, except for some custom entities, such as contract agreements and obligations.<\/p>\n AMT is organized around cloud services, Azure services, and our corporate network. Because SAP lives on-premises in our corporate network, Microsoft Digital created a hybrid connectivity solution to facilitate the flow of data from the cloud through our corporate firewall to on-premises systems. Figure 2 shows an overview of the solution.<\/p>\n In the\u00a0cloud<\/i>, we use Dynamics 365, SharePoint Online, and Microsoft Record Center. In these applications, documents are created, stored locally, digitally signed, and then stored in Microsoft Record Center. SharePoint Online is used for local data storage. AMT business processes collect documents and stores them in SharePoint Online until automated workflows are executed. DocuSign is the third-party component that digitally signs documents. Final output from the contract signing process is stored and kept in Microsoft Record Center.<\/p>\n In\u00a0Azure<\/i>, the CRM SAP Web Service and our hybrid connection create a path for different types of data\u2014such as agreement, SAP-specific, and fulfillment\u2014to flow from cloud-based AMT services to our corporate network and SAP. For example, specific agreement data used to create contracts, such as a business partner name, or an obligation identification code, needs to flow from AMT in the cloud, to SAP on-premises. The CRM SAP web service replicates AMT functions, and routes data back into internal systems for integration.<\/p>\n In the\u00a0Corporate Network,\u00a0<\/i>there are data staging services, a data mall for data storage and extraction, and on\u2011premises SAP. In the AMT staging database, data is extracted from corporate invoicing and customer data stores, and then ported into a staging database. This is where SQL jobs and tasks\u2014such as data transformation and data aggregation from multiple sources\u2014occur. The data mall is a repository for distributed systems, such as customer and invoicing data. Once the transformation and aggregation tasks are completed, the subset of data from the staging database is made available to AMT.<\/p>\n AMT streamlined multiple tools and repositories into a single system. It integrates SAP and our internal data staging warehouse for managing invoices and payments. AMT integrates with Feed Store, DocuSign, and the Microsoft Records Center. Out-of-the-box Dynamics 365 tools work with Microsoft systems such as SharePoint and Power BI.<\/p>\n There are two SAP integration points in AMT:<\/p>\n The DocuSign for Dynamics connector easily creates relationships between DocuSign and Dynamics CRM entities. Most of our integration was achieved with the standard DocuSign connector. Only 10 percent was customized for Advertising Operations business needs. We preconfigured \u201cSend for Signature\u201d actions with the right recipients so that documents in Dynamics 365 can be easily signed or sent.<\/p>\n The workflow progresses naturally from the contracting process. For example, in an agreement, the CRM user clicks a \u201cSend for Signature\u201d button. The user uploads and identifies specific documents that need to be sent for signature in DocuSign. We incorporated custom JavaScript because we didn\u2019t want to display all the default DocuSign buttons, and we applied a custom action to the button that people see.<\/p>\n When a user clicks our custom \u201cSend for Signature\u201d button:<\/p>\n AMT dashboards allow the business to closely manage the signature process. They track DocuSign transactions from beginning to end, and it\u2019s easy to see if an agreement is signed or not.<\/p>\n SharePoint integration is, for the most part, out of the box. We use SharePoint as a document repository. Whenever an agreement is created in AMT, two things happen. First, AMT uses a plug-in to dynamically create a corresponding SharePoint document library and URL. Then, a web app captures logs, reflecting the process. Embedded metadata routes documents to DocuSign or the Microsoft Records Center.<\/p>\n AMT was developed as an on-premises solution in 2013. In 2016, we moved it to the cloud. To make the move, a hybrid connectivity solution had to be created to move data between our cloud-based Dynamics 365 instance and on-premises SAP resources behind our firewall. We worked with the Azure Operations group on our hybrid connectivity solution, and it\u2019s now the standard across Microsoft.<\/p>\n When we moved data from Dynamics CRM to Dynamics 365, the transition was fairly smooth, as we followed a well-defined\u00a0process\u00a0of data cleansing and testing. The main challenge was integrating our on-premises SAP and our cloud configurations. In our original on-premises configuration, databases were directly connected. We had to incorporate hybrid connections into our Azure Web App and AMT staging databases, so that we could integrate with on-premises SAP system.<\/p>\n The hybrid connection created for AMT was the first at Microsoft, and set a precedent and standard for part on\u2011premises, part cloud configurations. We worked closely with Dynamics 365 product architects to make it happen.<\/p>\n It\u2019s designed in a reusable way that can be applied to other IT solutions in our portfolio that integrate with SAP or that need a hybrid connector. We\u2019ve created documentation for other teams on how to set up a hybrid connection, what to consider beforehand, and best practices.<\/p>\n The AMT solution offers Microsoft many business and technical benefits. They include:<\/p>\n Overall, the AMT solution evolved smoothly from its initial on-premises Dynamics CRM instance to the cloud\u2011based solution. There were some lessons that came out of the experience, such as:<\/p>\n Today, AMT applies to advertising operations. Going forward, we want to scale this business and then take on other business scenarios. We\u2019re poised to grow. Next year, we anticipate that AMT will process over a billion dollars. We\u2019re continuing to drive automation into our development processes, and UI automation will be incorporated.\u00a0AMT passes internal Microsoft Digital Security controls. Our next step is to adopt Sarbanes Oxley best practices.<\/p>\n We want to pilot other Microsoft businesses\u2014outside of advertising\u2014that have similar needs. There are many groups that process contracts. We want to use common connectors and features such as data export services, Azure Logic Apps, and common data models, to track and process them through AMT.<\/p>\n We look forward to integrating AMT with our advertising operations pre-sales Dynamics CRM system. This will give us an end-to-end view of advertising operations from pre-sales through post-sales and, ultimately, to the end of relationships.<\/p>\n We\u2019ve reimagined what a CRM can be. We\u2019ve created a scalable, economical, and reusable system to manage our advertising operations. In the process, we\u2019ve reduced support costs, standardized and automated workflows, and reduced errors. AMT has improved workflows for Advertising Operations using available programs and connectors. AMT contract and transaction management can apply to many other teams at Microsoft.<\/p>\n","protected":false},"excerpt":{"rendered":" This content has been archived, and while it was correct at time of publication, it may no longer be accurate or reflect the current situation at Microsoft. When managing advertising agreements became complex and error-prone, Microsoft Digital turned to Microsoft Dynamics 365 to create a contract life cycle solution. The system streamlined contract creation, approval, […]<\/p>\n","protected":false},"author":146,"featured_media":11127,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"_hide_featured_on_single":false,"_show_featured_caption_on_single":false,"footnotes":""},"categories":[1],"tags":[],"coauthors":[674],"class_list":["post-11125","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized","m-blog-post"],"yoast_head":"\nConfigure, don\u2019t customize<\/h3>\n
Architecture<\/h2>\n
Integrating other tools with AMT<\/h2>\n
SAP integration<\/h3>\n
\n
DocuSign integration<\/h3>\n
\n
SharePoint integration<\/h3>\n
Cloud migration and hybrid connectivity<\/h2>\n
What we\u2019ve gained from AMT<\/h2>\n
\n
Best practices<\/h2>\n
\n
Looking ahead<\/h2>\n
Key takeaways<\/h2>\n