Introduction: Ensuring user security is a crucial aspect in Dynamics 365 for Finance and Operations. To access or utilize the features of Dynamics 365 F&O, a user must have a role assigned to them. Without a role, the user will be unable to perform any actions within the system. Access levels and business processes for a particular role are determined by the duties and privileges associated with that role. In this blog post, we will explore two recently introduced features that simplify the process of comprehending and setting up customized security roles within Dynamics 365: security diagnostic and security configuration tools. Defining terms used in Security: Security Roles: – Security roles in Dynamics 365 define how users can access different modules. – The system comes with pre-defined security roles that can be assigned to users. A user has the ability to possess multiple security roles. – Data security policies can only be applied by the administrator to limit user access to data. – To gain access to Finance and Operations, it is mandatory for users to be assigned to at least one security role.  – Security roles correspond to company responsibilities and contain a set of duties required to carry out functions. Duties: – Duties correspond to tasks of a role and are part of a business process. – They are composed of privileges necessary for performing an action. – Duties can be assigned to multiple security roles and help reduce fraud and detect errors. – Segregating duties is important for regulatory compliance such as SOX and IFRS. – Default duties are provided, and administrators can modify or create new duties. Privileges: – Privileges are unit action sets that correspond to system functions. – They specify the level of access required to perform a job or complete an assignment. – Privileges refer to specific permissions granted to application objects such as UI elements and tables. – Default privileges are provided, and administrators can modify or create new privileges. Permissions: – Permissions are required for accessing functions in Dynamics 365. – Access levels are grouped for permissions to tables, fields, forms, or server-side methods. – Permissions include any tables, fields, forms, or server-side methods accessed through the entry point. Security Configuration Tool: The Security Configuration Tool is a useful tool for administrators as it enables them to create and manage security roles, duties, and privileges.  The Security Configuration Tool is a feature in Dynamics 365 that offers various benefits to users. Here are some of the benefits: Display Entry Point Permissions: The tool enables administrators to display entry point permissions for a given role, duty, or privilege. Test Security Role is a useful feature that allows users to check if a security role, duty, or privilege has been newly created or modified, without having to create a separate test user account.  Non-Permanent Changes: Changes made in the Security Configuration Tool are not permanent and must be published to take effect. Data Export/Import: Changes can be saved as a data export file that can be imported into desired environments. Full Hierarchy View: Users can access the tool by going to System Administration > Security > Security Configuration and have a full hierarchy view of roles, duties, privileges, and entry point security assignments. Duplicate Existing Roles: Users can duplicate existing roles, duties, and privileges. Various Options: The tool offers several options for performing against the currently selected role/duty/privilege, including undo/redo customizations, creating new roles, showing all levels, deleting roles, duplicating roles, copying roles, viewing permissions, and displaying the audit trail. To add a new role in Dynamics 365 with the Security Configuration Tool, you can follow these easy steps: Step 1: Select the ‘Roles’ tab and click ‘Create new’ to create a new role in Dynamics 365. Step 2: Enter the name of the new role using a different naming convention so that it is easily identifiable. Step 3: To add a new duty to a role, highlight it, go to the Duties column, and select Add references. All duties (and customs if created) will be available in the list. Step 4: You can select certain tasks, and their corresponding privileges, to be available in a role. If needed, users can remove certain tasks from the role. Step 5: To modify object permissions, go to the Privileges section. Dynamics 365 has different access levels, such as Read, Update, Create, and Delete, that determine a user’s level of access to a particular record or record type. Security roles have three types of access levels: Unset, Grant, and Deny. Step 6: Any modifications made in the user interface must be published before they are implemented. This list shows all the changes that are not yet published. Security Diagnostic Tool: The Security Diagnostic Tool is a unique feature of Dynamics 365 that empowers individuals with a security administrator or system administrator role to conduct an assessment on any form to identify the roles, duties, and privileges required to accomplish a task.  The tool provides numerous advantages to its users, including: To use the Security Diagnostic Tool, simply follow these steps: go to the Option tab, then select Page Options, and finally, click on Security Diagnostics.  This will automatically run the tool for you. Remember that the Security Diagnostic Tool is available on any form.  After the tool runs, it will generate a comprehensive list of all the roles, duties, and privileges related to that particular form.  This enables administrators to quickly identify any gaps in security and make necessary adjustments to ensure the protection of the system and its data. Conclusion: In conclusion, Dynamics 365 for Finance offers a reliable and secure role-based security system that guarantees that users have access to only the data that is necessary for them to carry out their tasks. The security roles, duties, privileges, and permissions collaborate to create a comprehensive security system that is effective.  Moreover, the security diagnostic and configuration tools make it simpler to comprehend and customize security roles in Dynamics 365. We hope you found this … Continue reading Security Roles in D365 Finance and Operation →

Introduction Small and medium businesses today have systems that were put in place based on the need back in time and served the purpose well. As organizations grow, they feel the need to consolidate information that is in these siloed systems. Siloed systems work well on their own but also pose challenges as business grows and more visibility into the systems is needed.   This article puts forward some thoughts on re-thinking siloed systems vs. integrated systems under one platform.  Challenges with Siloed Systems Need for Integrated Systems Conclusion   Read more about our Customer Success Stories. 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  

In the world of retail and commerce, managing sales returns efficiently is a critical aspect of customer satisfaction and operational excellence. In this blog, let’s explore how the sales return process works in Dynamics 365 Finance and Operations (D365FO) and explore how businesses can leverage the capabilities of this robust ERP system to streamline and enhance their return management. In this part, I will walk you through the standard process. Please keep in mind that the steps and setups may vary based on the business requirement. Let’s consider a scenario wherein we have sold 10 quantities to the customer and amongst them 3 quantities get damaged during transit. So now the customer wants to return those items back to us. So, lets create a Return Order, to do that go to Sales and Marketing>Sales Return>All Return Orders. Create a New Return Order. The RMA number is generated automatically based on the Number sequence set up. Tip: In order to generate the RMA Number manually you can enable the Manual number sequence parameter in the RMA Number Sequence set up. For this scenario, I have enabled the Manual Parameter. The next step is to Enter the Customer Details, Site, Warehouse, Return Reason Code and RMA Number. Then click OK. Now to add the line item on the Return Order line there are two ways to do it: For now, I will go with the Find Sales Order function. To use that go to the Return Order fast tab in that under the Return Tab click on the Find Sales Order button. The next step is to select the Sales Order Invoice for which the Return Order will be Created.   Based on my scenario the system has automatically taken the quantity as 3. In the above screen shot you can see that a New Return order is created with the Negative line quantity. Return Order processing: There are two ways to process a Sales Order Return: 1.Credit Only: In the credit-only process, the customer’s account is credited without the need for replacing or returning the item. Here, the Sales price is credited to the Customer deducting the charges. 2.Physical Return: The Physical Return process involves the Return of Item to the customer. Here during registration, a Disposition Code is assigned which determines the Sales Return process for that particular Item. To keep this simple and easy to understand I will go ahead with Credit Only process in this part. But for this we will first need to create a Credit Only Disposition Code. For that go to Sales and Marketing>Set Up>Returns>Disposition Codes. In that Click New and create a New Credit Only Disposition Code. Now the next step is to Register the Return order for that on the Return order lines click Update Line then under that click on Registration. Then select the Credit Only Disposition Code and click OK. Then Confirm the Registration. As I click on the Confirm Registration button a New Sales Return Order is created with the same quantity and same customer on the All-Sales Order page. The next step is to Invoice the Sales Return Order. After Invoicing the Sales Return Order, in the below screenshot you can see that the Return status of the order is changed to Invoiced. This completes the Credit only sales return order process. Maintaining customer satisfaction and operational efficiency in Sales and Marketing involves effectively managing sales returns. Dynamics 365 Finance and Operations (D365FO) simplifies this task, whether you opt for a credit-only strategy or handle physical returns. By leveraging D365FO’s powerful features, businesses can ensure precise and efficient return management, enhancing both customer relations and operational excellence. Stay tuned for the next section, where we’ll dive into the Physical Return process. 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:   For growing businesses, as much as their processes, reports, and efficient systems are important, service request management becomes equally crucial. As companies scale, the volume and complexity of service requests increase, making efficient management essential to maintaining operational flow and customer satisfaction.   A well-designed Service Request Management System (SRMS) helps align workflows, reduce response times, and enhance service delivery.    In this article, we will cover what such a system typically entails and why it’s vital for a growing business.   Let’s look at some of the key components that make an SRMS most effective.   Now that we have covered the key components, let us look at what a service request management system should be like for a growing business and how to set it up. Here are some key points to consider.   Every company should establish a support email address (support@companydomain.com) to facilitate customer queries. Customers typically prefer using a support email over a phone number or support portal, making it the most convenient method for logging service requests.   Process flow diagram for a SRMS  Conclusion:   Having a solid service request management system (SRMS) is a game-changer for any growing business. By centralizing your service requests, automating processes, and setting clear expectations with SLAs, you can keep things running smoothly and keep your customers happy. Features like real-time updates, automatic case assignments, and a self-service portal make life easier for both your team and your customers. With these tools, you can handle more requests efficiently, ensure quick resolutions, and maintain high service standards as your business grows. Investing in a good SRMS means you’re building a responsive and customer-focused business that can thrive even as it expands.  Here is our featured Customer Success Story:    Revolution Cooking partnered with CloudFronts for Dynamics 365 enhancements and data integration with the third-party applications.  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:  As a business owner, you might have come across a situation where you want to upgrade your current systems with renowned ERP solutions available on the market. One of the ERPs you would consider is Microsoft Dynamics. However, even choosing this would require a lot of brainstorming from all decision-makers because Microsoft Dynamics comes with two ERP platforms, i.e., Dynamics 365 Business Central and Dynamics 365 Finance & Supply Chain. I assume this brainstorming itself would have probably landed you on this article. Let’s dive into the key differences and use cases for each platform. Hopefully, by the end of the article, you will be able to make a decision and choose the right platform for your business.  Below are the key factors differentiating Dynamics 365 Business Central and Dynamics 365 Finance & Supply Chain: Company Size: When determining company size, the usual factors that are considered are revenue and employee count. The definition of which can change based on the country you are located in. Here, for reference, we would consider the following: – Revenue: a. SME: Having revenue between 0 and 1 billion USD. Business Central is ideal for this size of company. b. Large companies: Having revenue above 1 billion USD. Finance and Operations is the ideal platform for large organizations. – Employees: a. SME: having employees between 0 and 500. b. Large companies: having more than 500 employees. Number of Entities: If your company has multiple legal entities in multiple geographical locations across the world,a. Business Central is ideal for companies with a single legal entity or multiple legal entities in the same country. Business Central allows you to create and manage individual products and accounts for each legal entity; however, it cannot be managed centrally. b. Finance and supply chain are ideal for companies with multiple legal entities across the world. Finance & Supply Chain allows you to manage products and accounts centrally and release them centrally to each legal entity across the world. Business Operations: Does your company have streamlined and simple operations? a. Business Central can handle operations for companies with streamlined and simplified operations that do not require very detailed data capture or sophisticated reporting. b. Finance & Supply Chain captures detailed data, covers a lot more processes than Business Central, and hence can provide robust and detailed reporting. Future Growth: It is also important to consider what the growth plans are for your company. If you currently have 2–3 legal entities, you may be tempted to go with Business Central, as it comes with low implementation and operating costs, ease of use, and faster implementation timelines. However, ERP projects are not done frequently, and it is important that you consider future organizational plans. Let’s say you intend to expand over the next three to five years into multiple different geographical areas. You should think about finance and supply chain as your organization’s go-to platform since this will be a big, long-term investment. You might want to consider the following factors while making the decision: – Licensing: a. Since finance and supply chain are for large companies, they come with a minimum licensing requirement of 20 licenses. b. Business Central is perfect for small and medium-sized businesses (SMEs) because it only requires one license and has no minimum licensing requirements. – Implementation timelines:a. Finance and Supply Chain has a typical implementation timeline of 6 months or more, considering the size of the implementation and global rollout.b. Business Central can be up and running in 3–6 months.    Conclusion:  Choose Business Central if: You’re an SME seeking an easy-to-use, all-in-one solution with a lower upfront and operating cost.  Choose D365 Finance & Operations if: You’re a large enterprise requiring extensive functionalities, deep customization, and global capabilities.  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  The methodology selected plays a major role in the successful completion of projects, especially those that are complex like ERP and CRM implementations. To ensure that goals are reached, deadlines are met, and resource utilization is done effectively, project management methodologies offer an organized approach to project management and execution. Choosing the appropriate approach and being aware of it can make all the difference for businesses making these kinds of big investments.  Project Management Methodologies Important for Success in Delivering Projects  Choosing the right project management methodology is crucial when starting a new project. Every company has a unique operating model that is influenced by its industry standards, procedures, and culture. Established organizations often have set ways to plan and execute their day-to-day activities, and new projects added throughout the year must align with these existing practices.  Implementing a new ERP or CRM system is particularly challenging as it imposes additional demands on the existing resources. Companies must recognize that such projects will add new tasks to their employees’ daily responsibilities. Hence, before initiating such implementation projects, it is essential for organizations to internally align with the respective teams involved. This ensures everyone is prepared for the additional workload, which includes collaborating with the implementation partner, gathering necessary data, and extensively testing the new system—all while ensuring regular tasks are not neglected.  Key Steps to Ensure Project Success  Ensuring that you and your partner are aligned and understand exactly what to expect during the project delivery phase.  – Companies should review their partner’s way of working and set a mindset that the success of the project does not solely depend on their partner but is a joint effort from both parties.  – This would be getting an understanding of all the phases that are involved in delivering a successfully project. i.e. from the Requirement gathering, Development, Testing, Go-Live.   – The CloudFronts methodology, which we will elaborate below, requires involvement from both parties. CloudFronts Methodology  At CloudFronts we follow a Hybrid methodology, where some part of the project is done in an iterative way and some in a linear method:  Kick-off  The kick-off meeting is one of the most crucial parts of the project. During this call, both parties align their way of working, establish key stakeholders from each side, and set up an escalation matrix. The teams are briefed on important milestones and the policies involved in project delivery.  Requirement Gathering  During the requirement gathering phase, conducting small demo sessions helps users understand what to expect from the system right from the start. This clarity is vital for setting the right expectations and ensuring user engagement.  Development  The development phase at CloudFronts is done iteratively. Modules are developed and shared with clients early for testing. This approach allows for constant validation from end users, increasing the chances of project success. Client feedback is incorporated in short cycles, ensuring users feel engaged and confident that their inputs are valued.  User Acceptance Testing (UAT)  User acceptance testing is conducted with a copy of the client’s production data, allowing users to test the system with familiar numbers and values. This familiarity helps users understand what to expect from the system during real tasks, making the transition smoother.  Go-Live and Post Go-Live Support  Once all UAT signoffs are received, changes are moved to production servers, and the system goes live. Post go-live, a week of support is provided, with regular calls to monitor system usage, ensuring the deployed system is being utilized to its full potential.  Ensuring Project Success  For a project to be successful, several key points must be communicated to clients:  – Raising Concerns in a Timely Manner: Promptly addressing issues helps prevent small problems from escalating.  – Being Clear on Expectations: Clear communication about what is expected from the system ensures alignment between the client and the implementation team.  – Covering Edge Case Scenarios: Ensuring that edge case scenarios are considered and tested prevents unexpected issues post go-live.  Conclusion  The project management methodology selected and the level of cooperation between the client and the implementation partner are critical factors in the success of an ERP or CRM implementation project. Through dedication to a methodical approach, clear communication, and active involvement of all relevant parties, organizations can considerably enhance their likelihood of achieving project success. Our hybrid methodology at CloudFronts, which combines linear and iterative approaches, guarantees that we meet the specific needs of our clients and deliver projects that propel business 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  

Introduction: Businesses in the digital age depend on cloud platforms and ERP systems integrating seamlessly. Dynamics 365 Finance & Operations (F&O) and azure integration is one such potent combination. Numerous advantages, such as improved scalability, agility, and data-driven decision-making capabilities, are made possible by this integration. The step-by-step instructions for connecting Azure with Dynamics 365 F&O will be provided in this blog. Steps to achieve the goal: Step 1: Setting up Azure Services a. Create an Azure account: Sign up for an Azure account if you don’t have one already. b. Provision Azure resources: Set up the required Azure resources such as virtual machines, databases, storage accounts, and other services according to your needs. Below are few links to create azure account. https://learn.microsoft.com/en-us/answers/questions/433827/how-to-get-an-azure-account-without-credit-card https://azure.microsoft.com/en-in/free/students Step 2: Configure Azure Active Directory (AAD) a. Click on New on the App Registration page. Set the name and set the type like below screenshots. b. Once you click on Ok button you would get notification like below. c. Now go to API Permission and click on Add permission d. Select Dynamics ERP e. Select Delegated Permission f. Select all permission and then click on Add Permission g. After selecting this permission again add permission on the screen this time selected Application Permission. h. Now we have to generate client secret value. Just select Certificates and secret. i. You will see the below screen where you can generate a new client secret j. Once you click on new you will see below screen where you can set the date to which this secret key would be valid. Max validity is 2 years. k. This is how the secret value would look like just copy Value. l. Now copy the Directory ID and Application ID Step 3: Connect Azure Services to F&O a. Go to Finance and Operations and serach globally Azure Active Directory/Microsoft Entra ID b. And then click on New and add your client id over here and set User ID as Admin. Please Note you should have the admin access right if not this won’t work. Conclusion: Azure integration with Dynamics 365 Finance & Operations empowers businesses to streamline processes, unlock data insights, and achieve operational excellence. Next blog would be how to connect standard API on postman and perform get and post function. Stay tuned! 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: The 2024 Wave 1 release of Microsoft Dynamics 365 Business Central introduces a new feature called Page Scripting. This tool is designed to enhance User Acceptance Testing (UAT) by allowing users to record and replay their actions within the Business Central. This capability streamlines the UAT process by automating repetitive tasks and ensuring consistency across tests. Capabilities and Usage: The Page Scripting tool, records user interactions such as opening pages, entering data, and navigating through the system. These interactions can be saved and replayed, making it easier to validate the system’s behavior under various conditions. The tool records actions in a YAML file format, which can be shared and reused, promoting collaboration and efficiency. Let’s get started with how page scripting works: – Setup: To use the Page Scripting tool, users must have specific permission sets assigned. – Once these permissions are in place, users can access the tool by navigating to Settings and selecting the Page Scripting (Preview) action. The tool pane appears on the right side of the screen, allowing users to start a new recording or open an existing one. – When the user clicks on Page Scripting action, following screen opens up: – In that, user have an option to start a new recording or open existing recording. – User can start a recording by clicking on “New recording” or “Start new” button. – When user clicks on ” Start New/New recording” following page displays: – When new recording is started it captures every user action and input, including interactions with custom or third-party extensions. Users can track their steps, such as opening the Customer List page, selecting a customer record, and entering new sales prices. During the recording, users can delete the last recorded step if needed and can stop and resume recording as necessary. For Example: – Once all the steps are completed, user can stop the recording and save the file in YML format. – If the user wants to replay the recording, then simply user can click on open recordings, select the saved file and all the recorded script will appear on the right screen. – A recording can then be played, and all the recorded actions are executed in the web client. User will see an indicator if an action is succeeded or not as shown below: – User can Click on “Play” action, the system will automatically run the whole script and indicate (a green tick) if successful as shown in above image. Conclusion: In brief, the Page Scripting tool in D365 Business Central enables advanced customization, allowing users to optimize workflows, enhance user experience, and drive efficiency within the system. This tool offers valuable flexibility for businesses to tailor their operations to their unique needs and goals. 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

Client Requirement: Financial Reporting Year Change from Jan-Dec to Apr-March The last financial year is January2021 to December2022. Client has the requirement to change the year to April to March. The transition year needs to be from January 2023 to March 2024. In Microsoft D365 F&O, fiscal calendar can be of 15months, however, ledger calendar cannot be more than 12 months. Solution: 1.  Ledger calendar can be shorter than 12 months. 2. We need to do two-year end close process: a. For January 2023 to December2023 – 12 months b. For January 2024 to March 2024 – 3 months 3. Client can have regular financial year from April 2024 to March 2025 onwards. 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  Dynamics 365 Project Operations (PO) is a project management application within the Dynamics 365 suite. It is designed to manage project-related tasks, schedules, resources, and budgets. While they may include some financial functionalities, they often lack the comprehensive financial management capabilities that dedicated financial platforms offer.  In this article, we will explore several functions that Project Operations (PO) cannot perform as effectively as financial platforms like QuickBooks (QB) or Dynamics 365 Business Central (BC).  We will also discuss how to bridge this gap and create a seamless integration between Project Operations and these financial platforms.  Let’s first look at what Project Operations falls short of and what financial platforms like QuickBooks or Dynamics 365 Business Central can offer.  Accounting Functionalities  General Ledger Management: Financial platforms provide robust general ledger management, allowing for detailed tracking and reporting of all financial transactions across the entire organization.  Accounts Payable and Receivable: They manage accounts payable (AP) and accounts receivable (AR) efficiently, including invoicing, bill payments, and collections.  Tax Compliance: Financial platforms are equipped with tools to manage tax calculations, filings, and compliance with local and international tax regulations.  Financial Reporting: Financial platforms offer extensive reporting capabilities, including profit and loss statements, balance sheets, and customizable financial reports.  Audit Trails: Financial platforms maintain detailed audit trails of all financial transactions, which are crucial for internal audits and external regulatory audits. To leverage the Project Management features of Project Operations and the above-discussed features of financial platforms, businesses often choose to integrate both systems.  Integration Approach  Custom integration offers the utmost flexibility when connecting Project Operations with QuickBooks or Business Central. Several key considerations and entities are important to ensure a seamless integration: Data Mapping:  Tables: Identifying the key entities (Tables) such as projects, expenses, invoices, customers, vendors, contacts, and accounts that need to be synchronized between project operations and financial platforms.  Mapping: Map the fields and attributes of these entities between the two systems to ensure accurate data transfer and synchronization.  Tip: The best practice is to create mapping Excel for maintaining the table and column mappings between the systems.   Chart of Accounts (COA):  Chart of Accounts: Proper alignment between the chart of accounts in Project Operations and the financial platforms is necessary to facilitate accurate financial reporting and reconciliation.  Tip: Creating custom tables for your Chart of Accounts (COAs) and designating the financial systems as the source of truth for COAs is recommended. This approach offers flexibility to associate COAs with expenses, materials, roles, etc.  API Integration:  API Access: Check if the financial platforms offer APIs for integration.  Integration Points: Determine the integration points where data will be exchanged between the two systems, such as project creation, expense tracking, invoice generation, and payment reconciliation.  Data Flow:  Data Direction: Define the direction of data flow between Project Operations and financial platforms, ensuring consistency and integrity of data. The source and the target systems should be defined.  Real-Time Sync: Decide whether data synchronization will occur in real-time or through scheduled batch processes to meet business requirements. Currency:  Currency Conversion: Consider currency conversion requirements when dealing with contracts or transactions in multiple currencies.  Error Handling and Logging:  Error Handling: Implement mechanisms to handle data validation errors, inconsistencies, and exceptions during data transfer between systems.  Logging: Maintain logs of integration activities and errors for troubleshooting, audit trails, and compliance purposes.  Security:  Authentication: Implement secure authentication mechanisms to ensure data privacy and integrity during data exchange between systems.  Access Control: Define roles and permissions to restrict access to sensitive data and functionalities based on user roles and responsibilities.  Testing:  Testing: Set up a dedicated testing session to validate the integration setup, data mappings, and synchronization processes before deploying to production.  Integration process flow diagrams:  Create a process flow diagram for all the entities, for example below, is an integration process flow diagram for integrating Accounts, Contacts, Vendors from Project Operations to Quick Books.  In conclusion, while Project Operations is essential for managing the operational aspects of projects, it lacks the depth and breadth of functionalities offered by dedicated financial platforms.   Financial platforms provide accounting, regulatory compliance, advanced financial reporting, cash flow management, and more, which are crucial for the overall financial health and strategic planning of an organization.   Integrating these platforms with Project Operations tools leverages the strengths of both, ensuring efficient project management and robust financial oversight.  Here is our featured Customer Success Story:  Armexa, a leading US-based Industrial Cybersecurity Company, partnered with CloudFronts for Services Automation with Microsoft Dynamics 365 Project Operations and Business Central.   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