The Townsend Report from the InfoStrat Division of Serenic Software

The repository for DevOps for Dynamics 365 Customer Engagement https://github.com/devkeydet/dyn365-ce-devops Much has been written about how Microsoft Dynamics may be used to create software solutions using configuration to replace extensive coding needed for traditional software development.  This "low code" approach can save time and reduce costs for building and implementing business solutions for some scenarios. At the same time, development tools and processes for "low code" are not as mature as those for most software development, especially for large and complex projects with multiple developers.  The tools are catching up and Dynamics implementers and administrators are adopting best practices for rolling out Dynamics solutions.  One of the most important of these approaches is DevOps. The goal of DevOps is to shorten the time between software iterations by integrating development and operations processes.  One of the chief ways to accomplish this goal

By Ayesha Mirza, senior consultant at InfoStrat One of the key initiatives of customer service is to make tasks easier for both the customer and customer service agents. Customers want to find information and customer service agents have the need to process, absorb and promote information requests in order to provide an adequate customer experience. Streamlining this flow of information requires planning and a robust platform such as Microsoft Dynamics 365 to bridge the gap between the customer experience and agent activities. This post describes our approach and best practices to consider while implementing Microsoft Dynamics 365 Customer Service. ·          Strategy –  Plan out your implementation from the start. Define purpose, scale, budget, baselines, promotion, delivery, maintenance and escalation methods prior to kick-off. This will aid in clarifying internal and business expectations and help keep costs and schedule as pro

Microsoft Azure is one of the big three cloud computing services (along with Amazon Web Services and the  Google Cloud Platform  ) and has been growing rapidly for many years.  The following highlights key concepts for those who may be new to Azure.  These topics are geared toward a CIO or CTO rather than a network expert or developer who may be researching more advanced topics. Many of the cloud computing concepts explored here apply to Amazon Web Services and the Google Cloud Platform as well. What is Azure? Azure is the Microsoft brand for cloud computing services.  Some, but not all Microsoft Cloud products are purchased and managed through Azure.  The largest exception is Microsoft Office 365, the cloud version of Microsoft Office which is sold under its own brand and managed from its own console.  Similarly, Dynamics 365 runs in the Microsoft cloud but is not managed from Azure but rather from Office 365. Azure and Office 365 do overlap and interact to the extent that Azu

Government agencies often create blanket purchase agreements (BPAs) and indefinite date indefinite quantity (IDIQ) orders in order to simplify procurement, so that they can have a smaller number of bidders respond to requirements and to set prices for products and services that they know they will need in the future. Tracking these BPA and IDIQ opportunities in your customer relationship management (CRM) system is a bit different from tracking an individual contract opportunity.  While many of the data elements you track will be the same, you do not know the dollar value of the contract until orders are subsequently submitted. One decision for you to make in your reporting is to decide whether to include an estimated value for the BPA or to count it as zero dollars and assign the dollar value only to task orders.  If you choose to give the BPA a value and also each task order, some reports will end up double-counting the revenue because only won orders generate revenue. You m