Introduction Azure Blob Storage Lifecycle Management allows you to manage and optimize the storage lifecycle of your data. You can define policies that automate the transition of blobs to different access tiers or delete them after a specified period. This can help reduce costs and manage the data efficiently. This Blog shows how to set up and manage lifecycle policies: Steps to Create a Lifecycle Management Policy Access the Azure Portal: Sign in to your Azure account and navigate to the Azure Portal. Navigate to Your Storage Account: – Go to “Storage accounts”. – Select the storage account where you want to apply the lifecycle policy. Configure Lifecycle Management: – In the storage account menu, under the “Blob service” section, select “Lifecycle management”. Add a Rule: – Click on “+ Add rule” to create a new lifecycle management rule. – Provide a name for the rule. Define Filters: You can specify filters to apply the rule to a subset of blobs. Filters can be based on: – Blob prefix (to apply the rule to blobs with a specific prefix). – Blob types (block blobs, append blobs, page blobs). Set Actions: – Define the actions for the rule, such as moving blobs to a cooler storage tier (Hot, Cool, Archive) or deleting them after a certain number of days. – You can specify the number of days after the blob’s last modification date or its creation date to trigger the action. Review and Save: – Review the policy settings. – Save the policy. Key Points to Remember – Access Tiers: Azure Blob Storage has different access tiers (Hot, Cool, Archive), and lifecycle policies help optimize costs by moving data to the appropriate tier based on its access patterns. – JSON Configuration: Policies can be defined using JSON, which provides flexibility and allows for complex rules. – Automation: Lifecycle management helps automate data management, reducing manual intervention and operational costs. Conclusion By setting up these policies, you can ensure that your data is stored cost-effectively while meeting your access and retention requirements. 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 Integrating Salesforce with InforLN is a critical task for organizations looking to streamline their sales and billing processes. With the AIS Interface, businesses can efficiently manage data flow between these two platforms, reducing manual effort, enhancing visibility, and improving overall organizational performance. In this Blog, it shows the detailed information for integration between Salesforce to InforLN. The AIS Interface is intended to Extract, Transform and Route the data from Salesforce to InforLN. The steps for integration would be same for different entities. Many organizations need Salesforce to InforLN integration because of the below reasons: Event Scenario Pre-Requisites: Process Steps: On Demand Load Scenario Pre-Requisites: Process Steps: Conclusion Based on the above Integration scenarios Azure Developer can easily navigate for the integration implementation and they can choose between Event Driven or On-Demand based on the business requirement. This integration not only simplifies complex processes but also eliminates redundant tasks, allowing teams to focus on more strategic initiatives. Whether your organization requires event-driven or on-demand integration, this guide equips you with the knowledge to implement a solution that enhances efficiency and supports your business 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

In this blog post, we are going to create an Azure Logic App that reads blob content from Azure Storage and responds with specific data. We walked through the entire process, from setting up the Logic App in the Azure Portal to configuring actions and testing the workflow. This Logic App provides a seamless way to automate the retrieval and processing of data stored in Azure Blob Storage, showcasing the flexibility and power of Azure Logic Apps in building serverless workflows.  Use Cases  Data Processing Pipeline  – Scenario: A company collects data from various sources and stores it in Azure Blob Storage for processing and insights.  – Solution: Use a Logic App to trigger new data uploads, process the data, and send it to downstream applications.  – Benefits: Automates data processing, reduces manual effort, and ensures timely data availability.  Configuration Management  – Scenario: An organization needs to fetch and apply configuration files from Azure Blob Storage dynamically.  – Solution: Use a Logic App to handle HTTP requests for configuration data and respond with the necessary settings.  – Benefits: Centralizes configuration management, ensuring consistency and reducing errors.  Customer Support Automation  – Scenario: A support system needs to fetch specific information from stored documents to respond to customer queries.  – Solution: Use a Logic App to trigger API queries, retrieve relevant documents from Blob Storage, and send responses.  – Benefits: Automates common customer query responses, improving support efficiency.   Prerequisites  Note:  – To learn more about how to obtain a free Azure account, click on Azure free account to create Free Trial Account.  – To learn how to create Azure Blob Storage Account & Container can refer blog: How to create: Azure Blob Storage, Container and Blob – CloudFronts  Steps to Create a Logic App in Azure  Step 1: Create a Logic App  Step 2: Fill in the necessary details:     Note:  – Consumption Plan: Ideal for scenarios with unpredictable or low to moderate workloads, where you only pay for what you use.  – Standard Plan: Best for high-usage, mission-critical applications that require consistent performance, dedicated resources, and enhanced development capabilities.  Choosing between the Consumption and Standard plans depends on your specific requirements regarding cost, performance, scaling, and development preferences.        Steps to Upload File on blob        Create a Logic App to Read Data from Blob: Step-by-Step Guide   Step 1: Set Up Logic App Designer     Step 2: Add Blob Storage Action     Step 3: Configure Blob Storage Action     Step 4: Add Response Action & Configure     Step 5: Save and Test the Logic App     Step 6: Test your Logic App           Conclusion  With the help of Azure Logic Apps, you can easily build automated processes that connect to a wide range of services and applications. By following this guide, you have learned how to build a Logic App that reads data from Azure Blob Storage and responds with specific information. This foundational knowledge can be expanded to create more complex workflows, offering endless possibilities for automation and integration in your business processes.  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  

Creating a Log Analytics Workspace in Azure is an essential step for monitoring and analyzing data from various sources within your Azure environment. This guide will walk you through the process, providing clear instructions and tips to help you set up your workspace efficiently. Azure Log Analytics Workspace is a powerful tool that allows you to collect and analyze data from various sources within your Azure environment. It provides insights that help you monitor the performance, availability, and health of your resources. Setting up a Log Analytics Workspace is crucial for effective cloud management and optimization. Access the Azure Portal – Log In: Start by logging into the Azure Portal. – Look for Log Analytics: Type “Log Analytics Workspaces” into the top search bar and choose it from the drop-down menu. Create a New Workspace – Initiate Creation: Click on the “Create” button to start the process. – Resource Group: To arrange your resources, select an already-existing group or establish a new one. – Name: Enter a unique name for your Log Analytics Workspace. Review and Create – Review Details: Check all the details you have entered to ensure they are correct. – Create Workspace: Click “Review + create,” and after validation, click “Create” to deploy your workspace. – If you go to Logs, you will have the ability to query the logs: Benefits of using Azure Log Analytics Workspace Practical 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

Integrating Azure Logic Apps with the Common Data Service (CDS) opens up a world of possibilities for automating business processes and enhancing productivity within your organization. This blog will guide you through the steps to set up this integration, explaining the benefits and practical applications along the way. Azure Logic Apps is a powerful cloud-based service that allows you to automate workflows and integrate apps, data, and services across organizations. The Common Data Service, now known as Dataverse, provides a secure and scalable data storage solution that supports integration with various Microsoft and third-party applications. By integrating these two services, you can streamline data flow and automate complex workflows with ease. Prerequisites Before you begin, ensure you have the following: – An active Azure subscription. – Access to the Common Data Service (Dataverse) environment. – Necessary permissions to create and manage Logic Apps and CDS. Log in to the Azure Portal: Go to Azure Portal. Create a New Logic App: – Search for “Logic Apps” in the search bar. – Click on “Add” to create a new Logic App. – Fill in the required details (name, resource group) and click “Create”. Add a CDS Connector: – Once the Logic App is created, open the Workflow and Add one. – Click on “When a row is added” under Common Data Service triggers. – Sign in to your CDS environment and grant the necessary permissions. Configure the Trigger: – Select the relevant entity – Accounts and specify the trigger conditions – When a row is added. – Accordingly, when a record is added then create a Contact Record. – Save the Logic App Testing Out: Scenario – Create a new account in your Dynamics 365 / Power App. After a few moments, refresh and we see the contact has been created and assigned to the new Account. – So, we know our Logic App has run. Now let’s look at it in the Azure portal. Under Metrics, we see the Logic App has run. Why Integrate Azure Logic Apps with Common Data Service? 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

We are delighted to announce that BÜCHI Labortechnik AG, headquartered in Switzerland and widely regarded as a global pioneer in laboratory equipment and technology solutions, has renewed its longstanding partnership with CloudFronts through a BI Developer Managed Services Agreement (MSA).  BÜCHI Labortechnik AG is one of the largest solution providers in the world for R&D, quality control and production of laboratory technology. For more than 80 years, Switzerland-headquartered BÜCHI has been delivering world-class solutions for laboratory, industrial and parallel evaporation, spray drying, melting point, preparative chromatography, extraction, distillation & digestion, dumas, and near-infrared spectroscopy to meet the needs of customers around the globe. It operates its business through a fine network of branches, subsidiaries and affiliates spread across the globe.  Learn more about them at https://www.buchi.com/en   The foundation of BÜCHI’s partnership with CloudFronts was laid with the creation of a harmonious data integration mechanism and insightful data analytics reports, achieved through the utilization of Microsoft Azure Integration Services (AIS) and Power BI.  With this agreement, CloudFronts will focus on providing a dedicated BI Developer and ensuring that the necessary elements and commitments are in place to provide BÜCHI Labortechnik AG with proactive monitoring, rapid issue resolution, ongoing maintenance, and support. This agreement is the extension to the previous MSA which is a testament to the quality, commitment and passion of CloudFronts team.  About CloudFronts  CloudFronts is a Dynamics 365 focused Microsoft Solutions Partner helping Teams & Organizations worldwide solve their Complex Business Challenges with Microsoft Cloud. Our head office and robust delivery centre are based out of Mumbai, India, along with branch offices in Singapore & the U.S.  Since its inception in 2012, CloudFronts has successfully served over 500+ small and medium-sized clients all over the world, such as North America, Europe, Australia, MENA, Maldives & India, with diverse experiences in sectors ranging from Professional Services, Financial Services, Manufacturing, Retail, Logistics/SCM, and Non-profits.   Please feel free to connect with us at transform@cloudfronts.com  

We are delighted to announce that BÜCHI Labortechnik AG, headquartered in Switzerland and widely regarded as a global pioneer in laboratory equipment and technology solutions, has renewed its longstanding partnership with CloudFronts through a Managed Services Agreement (MSA) for Data Architect.  BÜCHI Labortechnik AG is one of the largest solution providers in the world for R&D, quality control and production of laboratory technology. For more than 80 years, Switzerland-headquartered BÜCHI has been delivering world-class solutions for laboratory, industrial and parallel evaporation, spray drying, melting point, preparative chromatography, extraction, distillation & digestion, dumas, and near-infrared spectroscopy to meet the needs of customers around the globe. It operates its business through a fine network of branches, subsidiaries and affiliates spread across the globe.  Learn more about them at https://www.buchi.com/en   The foundation of BÜCHI’s partnership with CloudFronts was laid with the creation of a harmonious data integration mechanism and insightful data analytics reports, achieved through the utilization of Microsoft Azure Integration Services (AIS) and Power BI.  With this agreement, CoudFronts will provide a dedicated Data Architect and will ensure that the proper elements and commitments are in place to provide ongoing Maintenance and Support to the Customer.  About CloudFronts  CloudFronts is a Dynamics 365 focused Microsoft Solutions Partner helping Teams & Organizations worldwide solve their Complex Business Challenges with Microsoft Cloud. Our head office and robust delivery centre are based out of Mumbai, India, along with branch offices in Singapore & the U.S.  Since its inception in 2012, CloudFronts has successfully served over 500+ small and medium-sized clients all over the world, such as North America, Europe, Australia, MENA, Maldives & India, with diverse experiences in sectors ranging from Professional Services, Financial Services, Manufacturing, Retail, Logistics/SCM, and Non-profits.   Please feel free to connect with 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

Microsoft Azure provides a cloud-based storage service called Azure Blob Storage. It is made up of Blobs, which are files kept as individual units and arranged like folders inside of Containers. Uses of Azure Blob Storage include: Steps to Create Azure Blob Storage STEP 1: Access the Azure Portal. Before proceeding, please confirm that you have a subscription. You will already have a FREE TRIAL membership for one month if you made a free account for the first time. Note: To learn more about how to obtain a free Azure account, click on Azure free account to create Free Trial Account. STEP 2: Setting up the “Storage Account” is the first and most important step in generating Blob Storage. Go into the Azure interface and select “Storage Accounts” to start the creation process. STEP 3: After clicking on Storge Account, the following screen will appear and then click on ‘+ New‘ to proceed further. STEP 4: After selecting New, you’ll be prompted to provide the following information on the following page: After you have entered all the information, click “Create.” Step 5: As seen in the sample below, an Azure Storage Account offers four different kinds of redundancy storage. For the demo, Geo-redundant Storage (GRS) will be used. Step 6: The next screen displays the deployment status when you click the “Create” button. Once deployment is finished, select “Go to resource.” Steps to Create Container STEP 1: Now, we have to create a new Container for that click on ‘+ Container ‘. Step 2: After selecting Add Container, a form requesting the container’s name (which must be unique) and access level will appear. We have chosen Blob Public Level access for the demo. Select “Create” to continue. Step 3: As a result, the blob storage has been effectively constructed, the container named as demo. Steps to Create Blob Step 1: Click on the container demo. Step 2: Under overview blob can be uploaded. The connection string can then be found by selecting the Storage Account and clicking on “Access keys.” These Connection Strings are used to communicate with the Storage Account. Conclusion Azure Blob Storage features integration with other Azure services, built-in security safeguards, and accessibility through a variety of tools and APIs. Azure Blob Storage is a solid and affordable solution for companies looking to store and manage unstructured data in the cloud thanks to these benefits, Azure Blob Storage is a powerful and flexible cloud storage option that offers several benefits. With many storage layers, it provides an enduring and scalable storage solution to satisfy the demands of diverse applications in terms of both cost and performance. 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