Introduction Seamless integration between systems is essential for efficient operations and data accuracy. One of the common integration challenges is syncing data between Customer Relationship Management (CRM) systems and Finance and Operations (FNO) systems. Traditionally, dual write has been a solution for this integration, but it comes with limitations. In this blog, we’ll explore a real-life business use case where we replace dual write with Azure Logic Apps to enable real-time data synchronization between CRM and FNO systems. Understanding Dual-Write Dual write is a framework provided by Microsoft that ensures data consistency between Dynamics 365 Finance and Operations (FNO) and Dynamics 365 Customer Engagement (CRM) applications. It facilitates real-time and bi-directional data synchronization, maintaining records of table and field mappings between FNO and CRM. This ensures that any change made in one system is reflected in the other, providing a unified experience across the enterprise. However, dual-write has its limitations, such as complex setup, limited customization options, and potential performance issues in high-transaction environments. These limitations prompt businesses to seek more flexible and scalable integration solutions. The Business Use Case: Replacing Dual-Write with Azure Logic Apps Scenario: A manufacturing company uses Dynamics 365 CRM to manage customer interactions and Dynamics 365 FNO to handle finance and operations. The company relies on dual write to keep customer data synchronized between the two systems. However, they face issues with the dual-write setup, including occasional synchronization lags and difficulties in customizing data mappings. To overcome these challenges, they decide to implement Azure Logic Apps for real-time data synchronization between CRM and FNO. Objective: Create a Logic App that enables real-time data synchronization between CRM and FNO, replacing the existing dual-write setup. This Logic App will ensure that any changes in customer data in CRM are immediately reflected in FNO and vice versa, without the complexities and limitations of dual write. Steps to Implement the Solution Benefits of Using Azure Logic Apps Conclusion By replacing dual write with Azure Logic Apps, the manufacturing company can achieve a more reliable and customizable integration between their CRM and FNO systems. This solution not only enhances data consistency and real-time synchronization but also provides the flexibility to adapt to future business requirements. Azure Logic Apps empower businesses to streamline their operations, improve data accuracy, and ultimately deliver better customer experiences. In our next blog, we will explore in detail how this business use case can be fully implemented using Azure Logic Apps. Stay tuned for a step-by-step guide on setting up the Logic App, configuring connectors, and ensuring seamless real-time data synchronization between CRM and FNO. We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

Introduction In Purchase & trade agreements in D365 – Part 1 blog we have gone through overview of Purchase & trade agreements in D365 & how to setup different types of Purchase agreements in D365. In this blog will go through how to setup purchase agreement of type Product category value commitment & Value commitment. To give brief overview of Purchase & trade agreements in D365, for those who have not gone through part 1 of this blog. In D365 we can create Purchase agreements for blanket orders to buy certain fixed quantity of item from specific vendor within specified time. & Trade agreement can be used to create discounts generally for short period for specific vendor or vendor group. In D365 there are different types of Purchase agreement & trade agreements. Below are different types of Purchase agreements based on commitment in D365 – Product category value commitment is setup when there is commitment to buy fixed amount of specific category of goods from specific vendor over fixed period & vendor provide discount%. For example, purchaser have committed to buy Travel luggage bags category SKUs from vendor A worth 10million over next 1 year then vendor will offer 20% discount for same. Value commitment when there is commitment to buy fixed amount from specific vendor over fixed period & vendor provide discount%. For example, purchaser have committed to buy from vendor A worth 15million over next 1 year then vendor will offer 20% discount for same. Below are different types of Trade agreements based on relation in D365 – Problem statement – In this scenario we need to setup purchase agreement of type Product category value commitment & Value commitment for vendor. Solution steps – 1 – Will create purchase agreement for Product category value commitment 1.1 Go to Procurement & Sourcing -> Purchase agreements -> Purchase agreements 1.2 Click on New -> Vendor account -> Select respective vendor (In this case it is VEN-000002) -> Purchase agreement classification -> Blanket purchase agreement -> Default commitment -> Product category value commitment -> Effective date -> Select respective date (In this case it is 1 Aug 24) -> Expiration date -> Select respective date (In this case it is 1 Aug 25) -> Ok 1.3 Fill the respective details of Item/Category name – Spinner, Net amount – 100000, Discount percent – 15 & Max enforced – Yes. Max enforced Yes means quantity consumed against purchase agreement is tracked. If purchase quantity exceeds quantity mentioned in agreement, then message will be displayed & link of Purchase agreement is removed from purchase order. & confirm purchase agreement. 1.4 Then create new Purchase order, select Purchase agreement to link 1.5 Add any Item with category mentioned in purchase agreement, in this case it is “Spinner” & required quantity in purchase order, discount will be automatically taken from purchase agreement. 1.6 We can check which agreement is linked, click on Update line -> Purchase agreement -> Attached. 1.7 Similarly, In Purchase agreement also same is reflected. 2 – Will create purchase agreement for Value commitment 2.1 Go to Procurement & Sourcing -> Purchase agreements -> Purchase agreements -> Click on New -> Vendor account ->  Select respective vendor (In this case it is VEN-000005) -> Purchase agreement classification -> Blanket purchase agreement -> Default commitment -> Value commitment -> Effective date ->  Select respective date (In this case it is 1 Aug 24) -> Expiration date ->  Select respective date (In this case it is 1 Aug 25) -> Ok 2.2 Fill the respective details of Item/Category name – can select highest category in this case it is Bags, Net amount – 500000, Discount percent – 20 & Max enforced – Yes. Max enforced Yes means quantity consumed against purchase agreement is tracked. If purchase quantity exceeds quantity mentioned in agreement, then message will be displayed & link of Purchase agreement is removed from purchase order. & confirm purchase agreement. 2.3Then create new Purchase order, select Purchase agreement to link 2.4 Add any Item with category mentioned in purchase agreement in this case it is “Bag” & required quantity in purchase order, discount will be automatically taken from purchase agreement. 2.5 We can check which agreement is linked, click on Update line -> Purchase agreement -> Attached. In this blog we completed purchase agreement types. In next blog (Part 3) will cover setup of trade agreement. We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

Introduction  In this blog post, I’ll walk you through the process of transforming JSON to JSON using Azure Logic Apps and the Liquid Template Language. This step-by-step guide will demonstrate how you can use Azure Integration Services to achieve your transformation goals.                                      What is Liquid Template Language?  The Liquid Template Language (commonly referred to as “Liquid”) is a flexible, open-source template language developed by Shopify. It is widely used to render dynamic content in platforms such as Shopify themes, Jekyll websites, and web applications. Liquid uses placeholders, loops, and conditional statements to pull dynamic data into a web template, making it an effective tool for JSON transformation.  Prerequisites  To complete this tutorial, you’ll need:  Sample Input JSON  We will use the following sample JSON file for this tutorial:  {    “FirstName”: “Deepak”,    “LastName”: “Ch”,    “Add1”: “T square, Saki Vihar Road, Andheri East”,    “Add2”: “Mumbai”,    “Landmark”: “Near Car Showroom”,    “PhoneNo1”: 9812727261,    “PhoneNo2”: 2121233322  }  Desired Output JSON  The client’s requirement is to transform the input JSON into the following format:  {    “Full Name”: “Deepak Ch”,    “Address”: “T square, Saki Vihar Road, Andheri East, Mumbai, Near Car Showroom”,    “Phone”: “9812727261, 2121233322”  }  Step-by-Step Guide –   Step 1: Create a Free Azure Integration Account  Step 2: Add the Liquid Template Map  Step 3: Create a Logic App  Step 4: Transform JSON to JSON using Liquid  Here’s the Liquid template used for this transformation:  {    “Full Name”: “{{content.FirstName}} {{content.LastName}}”,    “Address”: “{{content.Add1}}, {{content.Add2}}, {{content.Landmark}}”,    “Phone”: “{{content.PhoneNo1}}, {{content.PhoneNo2}}”  }      Step 5: Test with Postman  Final Output  The output JSON will be:  {    “Full Name”: “Deepak Ch”,    “Address”: “T square, Saki Vihar Road, Andheri East, Mumbai, Near Car Showroom”,    “Phone”: “9812727261, 2121233322”  }  We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

Introduction In today’s business environment, Companies must adhere to various financial reporting standards. These standards are essential for fostering investor confidence, ensuring regulatory compliance, and supporting international expansion. Depending on their operational scope, some organizations are required to comply with multiple reporting frameworks, often necessitating the maintenance of multiple books of accounts. Companies need to comply with Financial Reporting Standards – IFRS, UK GAAP, US GAAP, Ind AS, Local GAAP due to reasons like: Compliance with the reporting standards is mandatory for some companies while others may follow them as best practice. There can be scenarios where a company must maintain multiple books of accounts to comply with multiple reporting standards. Example: Company listed on multiple stock exchanges like Infosys, ICICI Bank, TCS (India and US stock Exchange) must prepare financial reports as per Ind AS and as per IFRS. Microsoft Dynamics 365 Finance has the capabilities to meet the financial reporting requirements. How D365 Finance supports Financial Reporting Standards: Thereby, a company can utilize D365 Finance to maintain separate books for Financial Reporting. Conclusion Compliance with various financial reporting standards is not just a regulatory necessity but also a best practice that can enhance investor confidence and facilitate global operations. Microsoft Dynamics 365 Finance simplifies this process by enabling organizations to maintain multiple charts of accounts, set up parallel posting layers, and customize financial reports to meet different regulatory standards. By leveraging the comprehensive capabilities of D365 Finance, businesses can efficiently manage their financial reporting requirements, ensuring compliance across multiple jurisdictions and fostering transparency in their financial operations. We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

Introduction Are You Quick Enough with Your Decision-Making? 73% of Businesses Say No. In today’s data-driven landscape, a whopping 73% of businesses confess they find it tough to make quick, informed decisions because their reporting tools are outdated or just not cutting it. Are you in the same boat? If yes, it might be time to rethink your strategy for gaining business insights. Meet Microsoft Dynamics 365 Business Central—a real game-changer for companies looking to turn their data into actionable insights. While many ERP systems come with basic reporting options, Business Central shines with its customizable reports that offer real-time data, greater flexibility, and predictive insights. In this blog, we’ll take a look at five standout reports in Business Central that not only provide essential insights but also empower your business to make quicker, smarter decisions. These reports are crafted to keep you ahead of the competition and help you hit your business targets—without the hassle of complicated customizations. Let’s jump in and see how these powerful reports can revolutionize your operations! 1. Dimension-Based Reporting: Custom Insights Without the Complexity Business Central makes that easy with dimension-based reporting. It allows you to slice and dice data across custom dimensions such as department, product line, project, or location. You don’t have to adjust your chart of accounts for every new need—you just define dimensions and filter reports accordingly. Imagine the insights: Want to know how profitable a particular product line is in a specific region? Or how a department is performing across multiple locations? With dimension-based reporting, you can quickly analyse performance across all these areas. 2. Account Schedules: Build Custom Financial Reports Without External Tools If financial reporting feels rigid or limited with your current system, then you’ll love Business Central’s Account Schedules. Picture this: You’re able to customize income statements, balance sheets, or cash flow reports to match your exact business needs. Whether you want to compare actuals vs. budgets by department or break down profitability by project, Account Schedules gives you the flexibility to design these reports yourself. 3. Seamless Integration with Power BI: Turn Data Into Visual Dashboards Are you tired of static reports that don’t tell the full story? Business Central’s seamless integration with Power BI allows you to transform raw data into rich, visual dashboards that offer deeper insights. You can create interactive, real-time dashboards that not only display your data but also allow you to drill down for detailed analysis. 4. Embedded Excel Integration: Collaborate and Update in Real-Time Do you find yourself constantly exporting data to Excel, only to struggle with re-importing it back into your system? Business Central solves that with its embedded Excel integration. Imagine this scenario: You export your financial data to Excel, update it with your team, and then push the updated data back into Business Central—with no data loss or formatting issues. The integration keeps all your financial and operational reports intact, so collaboration is seamless. 5. Cash Flow Forecasting with AI: Predict the Future of Your Finances How accurate are your cash flow forecasts? With Business Central, you get AI-driven cash flow forecasting that goes beyond simple historical analysis. The system uses machine learning to predict future cash flows based on past data, outstanding receivables, and planned expenses, giving you a clearer picture of your financial future. Ready to See These Reports in Action? These reports are just the beginning. With Microsoft Dynamics 365 Business Central, you have a powerful tool that helps you make smarter, quicker decisions and stay ahead of the competition. Interested in learning how Business Central can transform your reporting? Reach out to us today for a personalized demo or consultation at transform@cloudfronts.com, and let’s explore how we can tailor these reports to fit your business’s unique needs.

Introduction In many businesses purchase is common & important function. & for purchase department, agreement is important feature. In D365 we have different types of agreements. i.e. Purchase agreement & Trade agreement. Both agreements have its benefits. In this blog will go through overview of purchase & trade agreements in D365 & setup of Purchase agreement in D365 of type Product quantity commitment & Product value commitment. In D365 we can create Purchase agreements for blanket orders to buy certain fixed quantity of item from specific vendor within specified time. Whereas Trade agreement can be used to create discounts generally for short period for specific vendor or vendor group. In D365 there are different types of Purchase agreement & trade agreements. Below are different types of Purchase agreements based on commitment in D365: Product quantity commitment is setup when there is commitment to buy fixed quantity of item from specific vendor over fixed period, so vendor will provide special purchase price for that quantity over defined period. For example, purchaser have committed to buy 1000 quantity of 1 SKU of luggage bag from vendor A over next 1 year then vendor will offer special price of 2000 instead of original price of 3000. Product value commitment is setup when there is commitment to buy fixed amount of specific item from specific vendor over fixed period & vendor provide discount%. For example, purchaser have committed to buy 1 SKU of luggage bag from vendor A worth 1million over next 1 year then vendor will offer 15% discount for same. Product category value commitment is setup when there is commitment to buy fixed amount of specific category of goods from specific vendor over fixed period & vendor provide discount%. For example, purchaser have committed to buy Travel luggage bags category SKU’s from vendor A worth 10million over next 1 year then vendor will offer 20% discount for same. Value commitment when there is commitment to buy fixed amount from specific vendor over fixed period & vendor provide discount%. For example, purchaser have committed to buy from vendor A worth 15million over next 1 year then vendor will offer 20% discount for same. Below are different types of Trade agreements based on relation in D365: Trade agreement for Purchase price is used to define purchase price of item from specific vendor or group of vendors. The price defined in trade agreement will be reflected in purchase order automatically. Trade agreement for Line discount for purchase is used to define discount on purchase price of item. can setup different types of discounts i.e. Fixed amount, percentage discount or for quantity range. Trade agreement for Multiline discount for purchase is also used define discount on purchase price of item but in multiline discount system will consider quantity of specified item available on multiple lines in purchase order to decide discount percentage. For example, If we have same range for line & multiline discount of 5% for 1-101 & 10% for 101-501. When Purchase order has 2(or multiple lines) of same item. i.e. 1st line has 50pcs & 2nd line has 70pcs. So, in case of Line discount each line will get discount of 5% even though total quantity is greater than 100. But in case of Multiline discount, discount applied will be 10% as total is greater than 100, as it considers total of multiple line. Trade agreement for Total discount for purchase is used to define discount percentage for total purchase order level & not at line level. Also note that, if both purchase agreement & trade agreement are defined for same combination of vendor & item, then Purchase agreement gets precedence / priority over trade agreement. Problem statement: In this scenario we need to setup Product quantity commitment & Product value commitment type of purchase agreement for vendor. Solution steps: 1 – Will create purchase agreement for Product quantity commitment 1.1 Go to Procurement & Sourcing -> Purchase agreements -> Purchase agreements 1.2 Click on New -> Vendor account -> Select respective vendor (In this case it is VEN-000001) -> Purchase agreement classification -> Blanket purchase agreement -> Default commitment -> Product quantity commitment -> Effective date -> Select respective date (In this case it is 1 Aug 24) -> Expiration date -> Select respective date (In this case it is 1 Aug 25) -> Ok 1.3 Fill the respective details of Item number – P-000003, Quantity – 1000, Unit price – 3000 & Max enforced – Yes. Max enforced Yes means quantity consumed against purchase agreement is tracked. If purchase quantity exceeds quantity mentioned in agreement, then message will be displayed & link of Purchase agreement is removed from purchase order. 1.4 Confirm purchase agreement. 1.5 Now create new purchase order. Go to Procurement & sourcing -> All purchase orders 1.6 New -> Select Vendor -> Select above created Purchase agreement -> Ok. 1.7 Add Item mentioned in purchase agreement, in this case it is P-000003 & required Quantity 500 in purchase order, price will be automatically taken from purchase agreement. 1.8 We can check which agreement is linked, click on Update line -> Purchase agreement -> Attached. 1.9 Similarly, In Purchase agreement also same is reflected. 2 – Will create purchase agreement for Product value commitment 2.1 Go to Procurement & Sourcing -> Purchase agreements -> Purchase agreements -> Click on New -> Vendor account -> Select respective vendor (In this case it is VEN-000001) -> Purchase agreement classification -> Blanket purchase agreement -> Default commitment -> Product value commitment -> Effective date -> Select respective date (In this case it is 1 Aug 24) -> Expiration date -> Select respective date (In this case it is 1 Aug 25) -> Ok 2.2 Fill the respective details of Item number – P-000003, Net amount – 50000, Discount percentage – 10 & Max enforced – Yes. Max enforced Yes means quantity consumed against purchase agreement is tracked. If purchase quantity exceeds quantity mentioned in agreement, then message will be displayed & link … Continue reading Understanding Purchase & trade agreements in D365 – Part 1 →

If you’re finding it challenging to decide when to use Azure Service Bus Queues or Topics, this blog is for you! In our previous blog, we explored Azure Service Bus Queues, Topics, and Subscriptions. To recap, Azure Service Bus is a fully managed messaging service provided by Microsoft Azure. It helps decouple and scale applications by allowing different components to communicate with each other through messages. In this blog, we will delve deeper into Azure Service Bus Queues vs. Topics, examining their differences, use cases, and how to choose between them based on your application needs. By understanding these core concepts, we’ll be better equipped to design scalable and efficient messaging solutions using Azure Service Bus. Azure Service Bus Queues vs. Topics Service Bus Queues Queues work on a First In, First Out (FIFO) basis. This means that clients that receive messages from the queue and then process that message in the order in which they were added to the queue, and they will be the only consumer that processes this message. The queue will store this message until our client is able to process them. To process the message, the client will pull the message off the queue. Purpose: Queues are designed for point-to-point communication. They are ideal when a single consumer needs to process messages from a single sender. Message Handling: Messages are stored in a queue and processed by a single consumer in a first-in, first-out (FIFO) manner. Use Case: Best suited for scenarios where a specific task needs to be handled one at a time. For example, in an order processing system where each order needs to be managed sequentially. Fig – Message Queue with Messages One of the benefits of using queues is that producers and consumers do not need to exchange messages simultaneously. Messages are stored in the queue and are processed only when the consumer retrieves them. This setup enables producers to continue sending messages to the queue independently. Consequently, components within our architecture can be decoupled, as producers and consumers are not required to synchronize their actions. If there is a high volume of messages entering the queue, we can scale up the consumers without needing to scale the producers. Service Bus Topics Topics are different to Queues since instead of working with a single consumer, we can have multiple subscribers to our topic, who will receive their own copy of the message from the topic. This works in a pub/sub pattern, where we will have messages being published to the topic and have multiple clients subscribe to that topic. Purpose: Topics are designed for publish-subscribe communication. They allow messages to be sent to a topic and processed by multiple consumers. Message Handling: Messages sent to a topic are delivered to multiple subscriptions. Each subscription can have its own filter and process messages independently. Use Case: Ideal for broadcasting messages to multiple systems. For instance, a CRM system might need to notify various departments (e.g., sales, marketing) about a new customer record. Fig – Topic with three Subscription with Messages In Topics, our consumers don’t directly consume the message from our Topic. Instead, we create subscriptions that subscribe to the topic and our consumers receive a copy of a message from the topic. In Azure Service Bus, we can define filters on these subscriptions that determine conditions for messages to be published to a subscription and actions that modifies the message metadata. Conclusion In this post, we discussed the differences between Queues and Topics in Azure Service Bus. To summarize, Azure Service Bus Queues are ideal for point-to-point communication in which messages must be handled sequentially by a single consumer. Topics, on the other hand, are suitable for scenarios that need publish-subscribe patterns, as they enable several consumers to process the same message independently. Choosing the proper solution is determined by your application’s, individual requirements, ensuring that your message system is both scalable and efficient. If your system requires sequential processing and single customers, queues are the best option. However, if your system wants to broadcast messages to several users, Topics will give the necessary flexibility and scalability. We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

Problem Statement  After an implementation has gone live, do we experience that the user participation tapers off before starting to decline? That’s when we feel the need to have an adoption strategy and metrics into place.  Strategizing User Adoption  Here are some thoughts on thinking about how to plan for User Adoption –   User Adoption Measurements  Here are some of the measurements and steps to take for User Adoption –   Conclusion  When you measure user adoption through trackable metrics and numbers, you can monitor the implementation’s success path.  This helps in rethinking the implementation and taking corrective action before the implementation itself is in question and why was it planned in the first place. Participation of partners, peers and all stakeholders share equal responsibility to make the implementation a resounding success.  We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

How to do Inventory closing and Recalculation? In D365 Finance & Operations, inventory closing, and recalculation are essential process and recommended to be part of the month close standard operating practices. In case these practices are not followed, companies may face issues like inventory miscalculations, inconsistent inventory values in defined dimensions. Go to Inventory Management>Periodic Tasks>Closing and Adjustment. Then from the Action tabs click on Close Procedure dropdown, in that click on Close Inventory. After clicking on the Close Inventory a dialogue box will open in that select the Closing Period Code. Then under the Post-Closing you can see the Run Recalculation after Closing parameter, enable this and then click OK for Inventory Closing. Enabling this parameter will Run the Recalculation right after the Inventory Closing. After clicking OK the system will run the Closing and Recalculation Batch Job. This is how the Inventory Closing procedure takes places in D365 Finance and Operations. What happens by Inventory month close and Inventory Recalculation: – Inventory Month Close: The system generates inventory closing journals and settlement entries for the closed transactions resulting into adjustments to update inventory accounts like inventory value and cost of goods sold. It blocks the inactive dimensions from being considered into any of the valuation process. – Inventory Recalculation: The system does an inventory revaluation to adjust inventory values based on the latest costs, market values and inventory valuation method selected (FIFO, LIFO, Weighted Average, Standard Cost). By including inventory month close and revaluation as part of the month end SOPs, companies can achieve efficient inventory management. Conclusion: Inventory closing and recalculation in D365 Finance & Operations are critical processes for maintaining accurate inventory values and ensuring smooth month-end procedures. By performing these tasks regularly, businesses can prevent discrepancies, update inventory accounts effectively, and reflect true inventory costs based on the chosen valuation method. We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

Introduction In Dynamics 365 CRM, integrating with external systems, running automated processes, and developing custom applications often requires non-interactive access to CRM data. One of the most secure and efficient ways to achieve this is by creating an Application User via the Azure Portal. In this blog, we’ll guide you through the step-by-step process of setting up an Application User and explain when and why you should use it in your CRM environment. Steps to Create an Application User: – Navigate to the Azure Portal and log in with your Azure account. – Search for Azure Active Directory or select from the left-hand menu. – Click on “App registrations” in the Azure Active Directory blade and click on “New registration”. – Enter the following details: – Click “Register”. – Select the newly created application from the App registrations list and click on “API permissions” in the left-hand menu. – Click on “Add a permission”. – Select “Dynamics CRM”. – Select “Delegated permissions” and check the necessary permissions such as user_impersonation. – Click “Add permissions”. – Click on “Grant admin consent for [your organization]” and confirm. – Go to “Certificates & secrets” in the application settings. – Click on “New client secret”. – Add a description (e.g., “CRM App Secret”) and set an expiry period. – Click “Add”. – Copy the value of the client secret and store it securely. You will need it later. – Add Application User in Dynamics 365 CRM – Log on to the Microsoft Power Platform Admin (D365 Admin) centre as a system administrator. – In the navigation pane, go to Environments, and then select an environment form the list. – On the Settings tab, go to Users + permissions, and then select Application users. – The application users page appears. – Click + New app user. – After clicking on + New app user. A side menu slider will appear. Here you will have to: When to Use an Application User Conclusion Creating an application user in Dynamics 365 CRM via the Azure Portal is a straightforward process that enhances the integration capabilities and automation potential of your CRM environment. By following the steps outlined above, you can set up an application user and leverage it for various integration and automation scenarios. We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com