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 In multinational companies having different hierarchy for purchase, i.e., in some companies, purchase is made at regional level, but in some companies, purchase is made at headquarter level by consolidating all regional requirements to have higher buying power and economies of scale and to maintain the same quality of goods over all regions. In a multientity environment having separate sets of employees for each legal entity and only headquarter employees having purchasing authority for all regional entities, the decision of inventory is taken by regional entity employees. In this case, each region submits a requirement to headquarters. In this case, to post and report on what and how much purchase was made for the respective regional entity, we need to create a purchase requisition for the respective buying legal entity. i.e., USMF is the headquarters entity, and PM is the regional entity. Problem statement While creating Purchase requisition from headquarter employee’s login, it is created with buying legal entity as headquarter entity. i.e. Julia is an employee of the headquarters USMF entity who will be going to issue the purchase requisition, and Mahesh is an employee of the regular entity PM. When we login to the PM entity from Julia’s login and create a purchase requisition, then the entity will automatically change to USMF. i.e., when a purchase requisition is made for a PM entity through Julia’s login with details given by Mahesh, it should remain for the PM entity, but the entity changes to USMF. & hence purchase requisition is registered at USMF. Follow the below steps in order to create a purchase requisition with a buying legal entity as per information given by respective regional entity employees and to maintain all details on the respective entity. i.e., details given by Mahesh for purchase requisition will be maintained on PM entity. Needs to add Mahesh name as requester for PM entity in Julia’s account. Go to Procurement & Sourcing > Setup > Policies > Purchase Requisition Permissions > 2. Then the below screen will appear. By preparer, choose Julia. Requester: Add all required employees of the PM entity, i.e., Mahesh, Jodi, Charlie, Ramesh, etc. 3. Go to Procurement & Sourcing -> Purchase Requisitions -> All purchase requirements and create new Purchase requisition from PM entity & click on requester, then all above added names will be available for selection. 4. And now if we add requester as Mahesh or any other name from the list, then a purchase requisition will be created for the PM entity, and the window will not switch back to USMF. Now all items added to this purchase requisition will be ordered and maintained for the PM entity. Conclusion For businesses with multiple legal entities, appropriately configuring purchase requisition permissions in Dynamics 365 guarantees that purchases are correctly attributed to the appropriate legal entities. This method improves reporting accuracy at the regional levels while also streamlining the procurement 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 There are 100 million developers around the globe who use Git. However, if you want to work with customizations in Finance and Operations, you need to learn how to use TFS. Initially, I was frustrated and confused about this requirement, but as I learned more about how projects are structured both locally and in TFS, things started to make sense. TFS (Team Foundation Server) is Microsoft’s take on source control management, continuously released and improved since 2005. TFS keeps the source code centralized and tightly integrated with the Microsoft ecosystem. Despite the differences, if you are familiar with Git, transitioning to TFS shouldn’t be too difficult. TFS shares similar concepts with Git, such as checking in, branching, merging, version tracking, and other standard features of a source control management system. Understanding these similarities can make learning TFS easier and help you leverage its full potential in Finance and Operations projects. Pre-requisites Configuration So, here we’ll be starting with a new project.(If you are working with an already created repository then you can skip ahead.) Now, I’ll be adding two folders here, “Main” and “Released”. Later, we’ll convert them into branches from Visual Studio. In TFS, we have the concepts of branches and in addition to that branches can contain folders as well. Folders are used for organizing files and do not impact the version control flow directly.They are simply a way to keep the repository structured and manageable. Branches here (similar to Git) are used to manage different versions or lines of development in the repository.They allow for parallel development and keep separate histories until changes are merged. Inside Main I’ve added a trunk folder as well. Now, let’s head into our Development Enviroment and connect this project to Visual Studio. I’ve clicked on “Continue without Code” for now. I’ll click on View and “Team Explorer” Here, it says “Offline” as currently there’s no Azure DevOps project connected to it.So, let’s do that! I’ll click on “Manage Connections” and “Connect to a Project” Here, as the project is hosted in my own organization on Azure DevOps,I’ll use the same credentials to log in. Here, we can see all the different projects I have created within my organization in Azure DevOps.I’ll click on the relevant one and click on Connect. Here, we see the 3 sections in the Team Explorer view. 1 – Which credentails are being used to connect.2 – The name of root of the project and where it is planning to download the content from TFS.3 – The different components where we’ll be doing most of our work once the initial set up is completed. For now, I’ll just click on “Map & Get” Here, we can see that the mapping was successful. Next, we click on the Source Control Explorer to see the actual content of the TFS server. Now, we can convert the “Main” and “Release” folders into Branches. We can do this by right clicking on the folder -> Branching and Merging -> Convert to Branch  After converting them to Branches, the icon next to them changes. Next, I’ll right click on my “Main” branch and add two new folders here. “Metadata” and “Projects” Now, before we can use these folders anywhere, we need to “push” these changes to the TFS.For that, we right click on “Trunk” folder and click on “Check in Pending Changes”. Now, we add a comment here describing what changes have been done (similar to a commit message)At the bottom we can see the files that have been created or modified. Once the check is done, we can see that the “+” icon next to the folders disappears and we get a notification that the checkin has been completed successfully. Now, this is where TFS shines through as better source control management for Finance and Operations. In (FnO) models and projects are stored in separate folders.  Using Git for this setup can be tricky, as it would either mean managing two different repositories or dealing with a huge .gitignore file.  TFS makes it easier by letting you map local folders directly to TFS folders, simplifying the management process. Here, we can see that currently, our mapping is a bit different than what we need, this is because of the “Map & Get” we did initially.So, to change that mapping, click on “Workspaces” Then click on “Edit” Now, we click on a new line to create a new mapping.Here, I’m creating a mapping between the “Metadata” folder in the “Main” branch of the TFS and the “PackageLocalDirectory” the place where all the models are stored for my system, Now, I’ll create another mapping between the Projects Folder and the local folder where my projects are stored. Now, once I click on “OK” it’ll prompt me if I want to load the changes. Click on “Yes” and move forward. But nothing changes here in Source Control Explorer. That’s because the Source Control Explorer shows what is stored in the TFS.And right now, nothing is; so we’ll have to add some models or projects here.Either we can add existing ones or we can create a new one.Let’s try to create a new model. Now, that the Model is created we’ll need to add it to our Source Control. Click on the blank space within the “Metadata” folder and select “Add Items to Folder” In the window, we can see that because of the mapping, we are sent to the local directory “PackageLocalDirectory”, and we can see our model inside it.Select that and click on “Next”. In the next view, we can see all the files and folders contained within the selected folder.Out of these, we can exclude the “Delta” folders. After, this we are left with these folders for the different elements.We can remove the content from the “XppMetadata” folders as well. Which leaves us with just the Description xml file. **Please do not exclude the descriptor file as without it Visual Studio will not be able to refer to your model or it’s … Continue reading CI/CD with TFS for Finance & Operations →

Introduction Postman is an essential tool for developers and IT professionals, offering a robust platform for testing APIs, automating test processes, and collaborating efficiently across teams. In this blog we’re going to connect Postman to our Finance and Operations environment so we can test out standard or custom APIs. This connection is a crucial step in ensuring that your APIs function as expected, and it helps streamline the integration of various business processes within your organization. Whether you’re new to API testing or looking to optimize your current setup, this guide will walk you through the process with clear, actionable steps. I’ve already covered automating the testing in Postman in my blog here so once the connections are in place you’ll be good to go! Pre-requisites Configuration We’ll start with creating an App Registration in Azure Portal. Go to the Azure Portal (of the same tenant of your FnO Environment). Search for “App Registration” and click on “New Registration”. Add a name for your new app and click on “Register.” Once it is completed, you’ll be taken to the Overview of the app. Here, click on the “Add a certificate or secret” under the “Client Credentials.” Add an appropriate name and select the expiration date of the certificate as necessary. Once you click on add you’ll get the confirmation message that the client credential has been created and you’ll be able to see the value of the secret. ** Be sure to copy this value and keep it securely as once we refresh from this page, this value will not be available. ** Now that everything is done on the Azure side, open your FnO environment and search for “Microsoft Entra Applications.” Click on “New.” Paste the “Application (Client) ID” into the “Client ID” field, then assign it a suitable name and a User ID.  The permissions given to the User ID will determine the permissions for the App. For now, I’ve assigned the “Admin” user. That’s all the configuration required at the FnO side. Now, let’s jump back into Postman. Now, in Postman we’ll start with a blank workspace and create a simple collection. The first thing that I like to do is to create different environments. As in FnO, we have a Production, a Sandbox and we can have multiple development environments so it may be possible that different environments are using different apps. So, to represent these environments, I like to create different environments in Postman as well. This is done by going to the “Environments” then clicking on “+” to create a new environment and giving it the appropriate name. Now, in this environment, I’ll add my app details as environment variables. The values for these can be found as follows –  “grant_type” can be hard coded to “client credentials” and we can leave “Curr_Token” as blank for now. So, at the end we get – We can also change the type to “Secret” so that no one else can see these values. Now, the necessary credentials have been added to Postman. Next, we’ll set up our collection for generating the Auth Token. For that, we’ll copy the “OAuth 2.0 token endpoint (v2)” from the “Endpoints” in our Azure App Registration’s Overview screen. In Postman, click on your Collection then “Authorization” then selects “OAuth 2.0” I’ll paste the URL we copied from the “OAuth 2.0 token endpoint (v2)” from the “Endpoints” in our Azure App Registration in the “Access Token URL” field and I’ll add my variables as defined at the Environment variables. If you get the error “Unresolved Variable” even after defining them, then it could mean that the Environment isn’t set as the active. So go back to the Environments list and mark it as active. This way we can easily swap between Environments. Once the environment is marked as Active, we can see that the variable is found correctly. I’ll also ensure that my Access Token URL refers to the tenant ID as per my variable by embedding my “tenant_id” variable in it. Next, I’ll click on “Get New Access Token.” If everything has gone well, you’ll be able to generate the token successfully. After that, you can give it a name and click on “Use Token” to use it. I’ll now create a simple API which we can use to test this token. Right click on the “Collection” and click on “Add Request” give it an appropriate name. The “{{base_url}}/data” returns a list of APIs available in the system. I’ve set the Authentication to “Inherit Auth from parent” which means it relies on the Authentication set on the “Collection” for calling the request as is shown on the right side of the screen. Here we see that the request was executed successfully. If for some reason, you cannot use the standard Postman way of generating the Token, you can create a seperate API responsible for generating the Auth Token, store it as a variable and use it in your requests. From here, you can use the generated “access_token” and pass it as a “Bearer Token” to your requests. Or you can select the entire token and set it to your “Curr_Token” variable. And then you can pass this variable to the requests like –  From Postman, we can then share these collections (which contain API data) and environments (which contain credentials) seperately as needed. All Data Entities follow the pattern – {{base_url}}/data/{{endpoint}} All services follow the pattern – {{base_url}}/api/services/{{service_group_name}}/{{service_name}}/{{method_name}} If I call a “Get” request on them, I get the details of the services for instance, here I’m getting the type of data I have to send in and the response I’ll be getting back in the form of object names. Moving back one step, I’m getting the names of the Operations (or methods) within this service object. Moving back one step, I’m getting the services within this Service Group. Moving back one step, I can see all the service groups available in the system. To actually run the logic behind the services … Continue reading Leverage Postman for Streamlined API Testing in Finance and Operations →

Introduction AL developers can now manage multiple file uploads at once in Business Central, significantly increasing flexibility. The AllowMultipleFiles property lets developers configure the FileUploadAction to accept either a single file or multiple files simultaneously. They can also specify acceptable file types using the AllowedFileExtensions property. This enhancement makes the file upload process more efficient and user-friendly. Pre-requisites Business Central (OnPrem/Cloud) References Handle Multiple File Uploads Configuration Here, for an example, a page extension that extends the “Resource Card” Page, adding a new list part to display uploaded files. File Upload Action: – AllowMultipleFiles: This property allows users to upload more than one file at a time. In the code example, it is set to true, enabling multiple file selection.AllowMultipleFiles = true; – AllowedFileExtensions: This property restricts the types of files that can be uploaded. In the code example, it allows only .jpg, .jpeg, and .png files.AllowedFileExtensions = ‘.jpg’,’.jpeg’, ‘.png’; – OnAction Trigger: Manages file processing: – Retrieves the highest entry number from the “Uploaded Files New” table. – For each file: The “Uploaded Files New” table stores the uploaded files’ metadata and content. It includes fields for entry number, resource number, file name, and file content. List Page for Uploaded Files The “Uploaded Files List” page displays the uploaded files in a list format, making it easy to view all files associated with a resource. In the above screenshot you can see the list of images which are uploaded. Conclusion This extension enhances the “Resource Card” by integrating a multi-file upload feature, making it easier to manage and access image files related to resources. The AllowMultipleFiles property lets users upload several files at once, while AllowedFileExtensions restricts uploads to specific file types like .jpg, .jpeg, and .png. It’s a simple yet powerful addition that improves usability and efficiency in 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

Introduction Search Engine Optimization plays a very important role in B2B lead generation. With that said there is always a question that comes to mind. How can we drive SEO to generate good business? The answer is, through genuine high-quality content. Writing and publishing high value content related to the nature of your industry which address the challenges and how did you help your client overcome those challenges always appeals to the audience and there are high probability chances that reading this content result in good conversions. How does Google Rank your page (On-Page Content Factor)?Google uses web crawlers to index pages and considers all the possible measurements to analyze and rank your content. – Genuine Content: As the web crawlers do their job of analyzing the content across the web, they check if the content is original or used from somewhere else. Is the content adding value to the topic. Is the content addressing the relevant queries and giving out the information that the audience needs. – In-depth Content: Always try to write genuine and relevant content, this creates enough awareness in the Google algorithm and then there are the chances of featuring high on the search engine page. – AI Driven Content: Google have always focused on the high-quality content. Use of AI should only be done to curate your own genuine content or create the content around your ideas with your own personal touch. Google’s guidance states that creating the AI generated content which does not focus on expertise, authoritativeness, experience and trustworthiness (E-A-T) is a violation of its spam policy because it is done to manipulate the search results. – Aesthetics of Content: And of course we should always consider the technical SEO aspect which includes, optimized title tag, relevant meta description, optimized header tags, internal links to keep the audience engaged. Optimize your website content, meta tags, headings, and URLs with the keywords. Ensure that your content addresses the specific pain points and questions your target audience has. How LinkedIn Rank your content?One of the key platforms in B2B world is LinkedIn Platform. It is important to stay relevant on LinkedIn to achieve business growth through content. – LinkedIn Algorithm assess posts every single day and recommends to the user based on the relevancy and the authenticity. – When we say the word assess, LinkedIn also always focus on high quality content which is easy to read, has minimal keywords, apt hashtags and based on these factors which content can gather more engagement. – LinkedIn also goes through your profile to evaluate your expertise and content that you are sharing. It should always be relevant to the nature of your work. This plays an important role in influencing the LinkedIn algorithm in ranking your content. – Engagement on LinkedIn is monitored where the algorithm goes through the comments of the post and check how the users are interacting. Are their comments relevant to the content posted, if yes LinkedIn then starts pushing the content to the broader audience. Content MarketingQuality content is crucial in the B2B space. Develop a content strategy which include Blogs Posts, Thought Leadership Articles, Whitepapers, Case Studies, and Win Wires. – Blog Posts: Regularly update with informative, engaging, and relevant blogs which can be technical or functional. Even a small blog can get you the lead that can deliver a great project to your organization. – Thought Leadership Articles: Thought Leadership Articles play a very vital role in the content strategy. This type of content written by the industry experts give out value added knowledge, insights and ideas, keeping the C-Level decision makers in mind. These types of articles should always be business driven and talk about the benefits the organization can get through improved ROI. Thought leadership content helps build and enhance the organizations brand reputation. It can differentiate them from competitors and attract potential clients, partners, or investors. – Whitepapers and E-books: Whitepapers often advocate for specific solutions, technologies, or approaches, persuading readers of their benefits and effectiveness. They serve as a resource for professionals and decision-makers, helping them make informed choices based on the information and analysis presented. – Case Studies: Showcase your success stories and provide practical examples of the challenges that were addressed and the solution that was implemented. Offer an in-depth narrative that includes background information, problem identification, solution implementation, and outcomes. Cases studies always highlight key learnings and best practices that can be applied to similar situations or challenges. – WinWire: Publish WinWire which provide specific details about the projects won, include the clients name, the products or services needed and the challenges to overcome. WinWire always serve as the validation of the company’s capabilities providing examples of the partnerships with some renowned clients across the globe. ConclusionIn conclusion, high-value content is a cornerstone of a strategic SEO approach in the B2B space, driving significant business conversions. By focusing on genuine, in-depth, and well-structured content, organizations can improve their visibility on search engines and platforms like LinkedIn, effectively reaching and engaging their target audience. Whether it’s through blog posts, thought leadership articles, whitepapers, or case studies, consistently delivering quality content not only enhances brand reputation but also fosters trust and credibility, ultimately leading to increased business opportunities and growth. 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

Introduction Accurate reporting and analysis require the consolidation of balances from various entities in complex financial environments. For this reason, Microsoft Dynamics 365 Finance and Operation provides strong tools that let businesses expedite their financial consolidation procedures. This blog will show you how to properly handle currency translation, set up elimination rules, and create a new entity for consolidation. You can make sure that your consolidated financial statements give a true and accurate picture of the financial health of your company by being aware of these procedures. To consolidate the balances of multiple entities, a new entity is created where the balances of the selected entities are consolidated and eliminated as per the requirement. In the Organization administration module>Organizations>Legal entities select Use for financial consolidation process and use for elimination process. Another part of set up is to create Elimination Rule:Create Elimination Journal by using the below screen: To run the consolidation process, navigate from the Main Menu to Consolidation -> Consolidate Online. The consolidation window opens, where the user can select the options as explained below: Go to the Legal Entities tab. Inside the legal entities, the user can select the entities to consolidate and the percentage of balances to be consolidated. Go to the Elimination tab. In the proposal options, keep the option as Proposal only. This will run the elimination of balances, but it will not post the amounts. The amounts will be posted to the ledger separately by the user. Add the elimination rule in the line. The elimination rule will eliminate balances based on 2 methods: Select the GL posting date for the date on which the elimination of the balances will be posted. Ideally this date will be the last date of the fiscal period. Go to the currency translation tab. The system will display the selected legal entities along with their base currency. At the bottom, select the exchange rate type. The exchange rate type will automatically convert the base currency of all entities to the base currency of the consolidation entity. In the above example, the exchange rate will convert INR and BRL to SGD. Note – This will work if the exchange rates are defined first. Lastly, click on OK. The system will run the consolidation process as a batch job and will provide the results in the trial balance after a few minutes. To verify the balances, open the trial balance for the fiscal period used in the consolidation. The TB will display the consolidated amounts of all entities in SGD only. For updating opening balances: General Journals to be used for updating opening balances For currency exchanges rates: Separate currency exchange rate type consolidation to used. In doing the currency translation, distinction should be made for monetary items and non-monetary items in the Balance Sheet. Normally, the latter should be part of Other Comprehensive Income (OCI). In the consolidation process, we can map different currency rate to different accounts through this screen. for Equity Method where only profit or loss has to be accounted in the consolidated entity, Journal entry has to be passed. Conclusion Maintaining financial accuracy and transparency in Finance and Operations requires successfully consolidating balances and establishing elimination rules. You can handle currency translation, properly apply elimination rules, and efficiently oversee the consolidation process by following the steps outlined in this blog. This strategy strengthens overall financial management within your company as well as the accuracy of your financial reports. 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 D365 Business Central, developers or system administrators have multiple user accounts. To ensure they are logged in with the correct account, they need to see the full username instead of just the initials displayed on the navigation bar. Let’s explore how to display the full username on the navigation bar. Pre-requisites Business Central onCloud Step-by-Step Guide to Configuring Username Display: Upon logging in to Business Central, the user’s profile photo will appear in the upper right corner. If the profile photo is not customized, it will automatically display the user’s initials. Open admin center Choose org settings under settings option Then click on Organization profile> Custom themes and then add new theme In Default theme you can see option to shows username on navigation bar Once above setting is done you can refresh your browser, now you can see full name on navigation bar. Conclusion For administrators and developers who oversee numerous accounts, specifically, personalizing the way usernames are displayed in D365 Business Central is a straightforward yet powerful method to improve user experience. You can quickly set up your navigation bar to display your full username, which will add clarity and guarantee that you are logged in with the correct account, by following the instructions in this guide. This minor modification can streamline your workflow and lower the possibility of errors, greatly improving your daily interactions with 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

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