In this blog, we will learn how to create an Azure Function App to connect it with Dynamics 365 CRM and perform the CRUD operation in Dynamics 365 CRM. First, we will create an Azure Function project for Dynamics 365 CRM from Visual Studio, and below are the steps for the same. Open Visual Studio and create a new Azure Function Project. Filter platform as Azure, select Azure Function, and click on Next. Name your project and click on Create button. After clicking on Create, you will get the below screen where you need to select the Trigger and Azure Function v1 (.Net Framework) and click on Create. In my case, the Azure Function trigger will be Http Trigger which means when an azure function will receive an HTTP request it will trigger. Your Azure Project will be created and the following will be the structure of the project. Now, we will create Azure Function to connect with the Dynamics 365 CRM we need to add the required NuGet Package [Microsoft.CrmSdk.CoreAssemblies]. To add the NuGet Package right-click on the Project and click on Manage Nuget packages. Add Microsoft.CrmSdk.CoreAssemblies in your Project. Following is the code to connect the Dynamics 365 CRM. Currently, we are going to use the credential by specifying them in the C# Code or you can use it as constant. Later in the series, we will learn how to use Environment Variable and pass the credential more secure way in Azure Function using Azure Key Vault. [Stay tuned..!!] Now, select the code and Refactor the code and make the connection function that will return the IOrganizationService if the connection is established else return null. Now, the final code will be as below: Now, we will create a customer with a Hardcoded name when the function is triggered with an HTTP request. Update the existing code with the below code: Testing: We will require the API testing tool, here I am using Postman and the following is the link to download “Postman”. https://www.postman.com/downloads/ To test the application, click on the Start button on top of Navbar as mentioned below in the screenshot [Button will have Project Name]. It will take a few minutes to Load the Azure Emulator Following is the screen you will be able to see and copy the URL highlighted in the red below and paste that URL in Postman. Open the Postman and click on the create a new tab; Select request as POST and paste the URL: After pasting the URL, click on Send You will get the following response on the Azure Function Tool and Postman If there any error or issue with the Azure Function code, the request will be failed and will be displayed on both Azure Function Tool and Postman [Status will be “4**” or “5**” ] Now, we will take look at Dynamics 365 CRM environment and check whether the account is created or not. We are justing getting started with Azure Function for Dynamics 365 CRM and stay tuned for more in this series. Upcoming blogs 1. How to use Dynamics 365 Credentials securely using Azures Function. 2. How to create Dynamics 365 integration with Third-party Applications. Many more……

Hello everyone in this blog we will see how we can post a message on a teams channel using logic app. Step 1: Go to portal.azure.com and select logic app azure service. Step 2:  Create a logic by filling the details accordingly. Step 3: Select the recurrence trigger for logic app Step 4: Now click on new step and select Ms Teams connector. Step 5: Select Post message on teams options. Step 6: Select your teams channel name and channel and write the message that you want to send. In this way you can post a message on teams. Hope this helps.

Azure Logic Apps is a cloud service that automates the execution of your business processes or workflows. It allows you to use a graphical design tool called the Logic Apps Designer to arrange pre-made components into the sequence you need. There are three ways in which we can create Logic App. Azure Portal – probably the most used form. Visual Studio – probably the favourite tool amongst developers. Visual Studio Code – with is getting more fans every day. Let’s Create logic app using Azure Portal Sign into the Azure Portal with your Azure account credentials. In the Azure portal search box, enter Logic Apps, and select Logic Apps. On the Logic Apps page, select Add. On the Logic App pane, provide the following details and then select Review + Create, and select Create. If you have more than one subscription, select the proper one from the Subscription combo box. On the Resource group, select an existing one or create a new one, but be aware that the Azure Resource group’s name must be unique inside your subscription. On the Logic App Name field, provide a name to your Logic App. Again, it has to be unique and can contain only letters, numbers, hyphens (-), underscores (_), parentheses ((,)), and periods (.). From the existing options, select the region where you want to store your logic apps on the Location field. You can also choose to enable Log Analytics to push the Logic App runtime events into it and help you monitor your workflows. After Azure successfully deploys your app, select Go to resource. Select a blank Logic app. To do that you need to select Blank Logic App under Templates and You can start defining your start building your sequence of tasks.

In order to create logic app using visual studio we should have VS Community edition or greater. Prerequisites Visual Studio 2019, 2017, or 2015 – Community edition or greater; Visual Studio Tools for Azure: In the Visual Studio installer, install Visual Studio (or modify an existing installation). Make sure the Azure development and ASP.NET and web development workloads are selected. Install Azure Logic Apps Tools for Visual Studio 2019 Open your Visual Studio, on the entry screen select the option Continue without code -> Then on the menu, navigate to Extensions > Manage Extensions Select Online and search for Logic Apps The add-in will be listed in the search results section. Click Download to download and install the add-in. You need to close your Visual Studio in order to begin installing this extension.  On the VSIX Installer screen Make sure that the correct version of Visual Studio is selected. Click Install or Modify.  This will download and install the add-in to your version of Visual Studio. At the end select Close.

The Logic Apps designer integrates with the current Azure Resource Group project so you can seamlessly work with resource deployments that include Logic Apps.  Open Visual Studio and on the Create a new project panel, select C# > Azure > Cloud, or select for Azure Resource Group; Select Azure Resource Group from the template list; On the Configure your new project panel, give a proper Project name, Location, Solution name, and leave the Framework as .Net Framework 4.7.2 and select Create. Finally, on the Select Azure Template panel, from the Visual Studio Templates list, select the Logic App template and select OK. This will create an empty Visual Studio Logic App solution. Now on the Visual Studio solution: Right-click on the LogicApp.json file and select Open With Logic App Designer This will open a Logic App Properties window, where you need to: Define the credentials to authenticate on the Azure subscription; Define the Subscription and Resource Group where you want to create these resources; Define if you want the Location to be in the same Region or in an Integration Service Environment (ISE) and click on OK; This will embed the Logic App designer inside the Visual Studio.

VS Code is the light weight and yet powerful editor to create logic app. In order to create logic app in VS code you must have Visual Studio Code 1.31.0 (January 2019) or later. To start with, first, you must install the extension from the marketplace. To do that, search Azure Logic Apps extension in the marketplace and Click on Install. Open your Visual Studio Code and bring up the Extensions view by clicking on the Extensions icon in the Activity Bar on the side of VS Code. And search Azure Logic Apps; After the installation of these extensions, you will find the two Azure Logic Apps section and then click on the Sign In Azure option. After you sign in then navigate to  your subscriptions and create new Logic app (for this you need to right click on the subscription and select create new logic app) This will open a small Logic App creation wizard on the top, in the center of the Visual Studio Code window, asking if we want to Create a new resource group or choose an existing one. If we select Create new resource group, then a new window appears asking for you to provide the resource group name Then we need to select a location to where the resource will be added In last step of the wizard will be providing a name for your Logic App

Azure App Configuration is a managed service that helps developers centralize their application configuration and feature settings simply and securely. Use Azure App Configuration to store and secure configuration settings for your application in a single location. App configuration offer the following benefits. A fully managed service that can be set up in minutes Flexible key representations and mappings Tagging with labels Point-in-time replay of settings Dedicated UI for feature flag management App configuration is useful in following Scenario. Centralize management and distribution of hierarchical configuration data for different environments and geographies Dynamically change application settings without the need to redeploy or restart an application Control feature availability in real-time The only problem was that unlike Key Vault, which has an available connector to be used inside Logic Apps, App Configuration doesn’t have a connector available. So in order to implement this scenario we’ll going to use Azure function app Create an Azure Function App: The Azure Functions project template in Visual Studio creates a project that you can publish to a function app in Azure. From the Visual Studio menu, select File > New > Project. In Create a new project, enter functions in the search box, choose the Azure Functions template, and then select Next. In Configure your new project, enter a Project name for your project, and then select Create. The function app name must be valid as a C# namespace, so don’t use underscores, hyphens, or any other nonalphanumeric characters. Select Httptrigger function app Connect to App configuration store: Right-click your project, and select Manage NuGet Packages. On the Browse tab, search for and add the Microsoft.Extensions.Configuration.AzureAppConfiguration NuGet package to your project. Add the following namespaces of the .NET Core configuration and the App Configuration provider. using Microsoft.Extensions.Configuration; using Microsoft.Extensions.Configuration.AzureAppConfiguration; The key that we want to read should be passed by query parameter. string appKey = req.Query[“appKey”]; And finally, the function should raise proper HTTP response status codes according to the situation: 200 Ok if successful returns a value for that key 500 Internal Server Error if something fails, for example, there is no connection string to the App Configuration defined and 404 Not Found if the key is not found Use below code for reference if(string.IsNullOrEmpty(appKey))                 return new BadRequestObjectResult(“parameter ‘appKey’ not found or empty.”);             try             {                 string connectionString = Environment.GetEnvironmentVariable(“AppConfigConnection”);                 var builder = new ConfigurationBuilder();                 builder.AddAzureAppConfiguration(connectionString);                 var build = builder.Build();                 string keyValue = build[appKey.ToString()];                 if (string.IsNullOrEmpty(keyValue))                 {                     var result = new ObjectResult(“Azure Configuration Key not found – ” + appKey);                     result.StatusCode = StatusCodes.Status404NotFound;                     return result;                 }                 else return new OkObjectResult(keyValue);             }             catch(Exception ex)             {                 var result = new ObjectResult(ex.Message);                 result.StatusCode = StatusCodes.Status500InternalServerError;                 return result;             } Once you create your Function App and all you key-values inside App Configuration, you have to: Go to your Function App Configuration option under Settings  And create a new application settings call AppConfigConnection containing the connection string to your App Configuration resource. Once we done that you can call Azure Function in your logic app

This blog will guide you through how the paginated data from API’s can be handled and Processed in Azure Logic App.

Microsoft Azure offer two different messaging services like Service Bus and Storage queues they are mainly used for to perform specific action or send response. Azure Service Bus It is the one of the oldest services of the Azure platform – it is a highly reliable, brokered cloud messaging system. This service is aimed for enterprise messaging scenarios and offers middleware technologies like message queueing and publish or subscribe messaging. Following are the capability for Service Bus Queues are offering an asynchronous messaging capability with first-in-first-out (FIFO) message delivery. Topics and subscriptions offer a similar capability as queues. However, there can be more consumers for messages that are sent to a topic. A topic has one or more subscriptions. Relay provides a gateway to connect on-premise services to Azure, without having to open a firewall connection to the network. Azure Service Bus is available in three tiers: Basic – queues and scheduled messages, and message size up to 256 KB. Standard – on top of basic with Topics and subscriptions, transactions, sessions, and de-duplication. Premium – on top of the standard, and message size up to 1 MB. How to Create Azure Service Bus Go to Azure Portal Click on New Resource and Select service bus component from Integration services. Select your Subscription, Resource Group and give a proper Name space and Select location. Select the Pricing tier as per convenient check the pricing https://azure.microsoft.com/en-in/pricing/details/service-bus/ Create namespace and add tags for resource as shown below A namespace is a scoping container for all messaging components. Multiple queues and topics can reside within a single namespace, and namespaces often serve as application containers. Review and Create the Service Bus Resource. Queues Messages are sent to and received from queues. Queues enable you to store messages until the receiving application is available to receive and process them. Messages in queues are ordered and timestamped on arrival. Once accepted, the message is held safely in redundant storage. Messages are delivered in pull mode, which delivers messages on request. Topics While a queue is often used for point-to-point communication, topics are useful in publish/subscribe scenarios. Topics can have multiple, independent subscriptions. A subscriber to a topic can receive a copy of each message sent to that topic. Subscriptions are named entities, which are durably created but can optionally expire or auto-delete. In some scenarios, you may not want individual subscriptions to receive all messages sent to a topic. If so, you can use rules and filters to define conditions that trigger optional actions, filter specified messages and set or modify message properties.

GitHub is a platform that is used by developers to work together on the same program at the same time. The underlying program is called Git and it keeps track of different versions and by giving support for merging conflicting modifications by different people. GitHub is an online hosting platform of code that you share through Git. Git is a command-line tool, GitHub adds an excellent web platform to share between developers and it also gives you an external backup of your code. Azure DevOps provides Git service that you need to complement your existing workflows. In order to getting started with Git go to below link and click on getting started with Git https://azure.microsoft.com/en-us/services/devops/ Click on new Project and select visibility to private Clone the local repo on DevOps once we set the repo we can then clone it to Visual Studio or any other IDE. We can see the different projects gets uploaded on DevOps Git repo service as shown below. The basic operations Below are the most basic commands/operations for Git that will allow you to get started easily: Clone: “downloading” an existing folder (called repository) of code on GitHub to your local computer so that you can work on it Commit: when you have made changes in your code repository, you must commit it before you can upload it to GitHub Push: when you have committed your changes, you then push them so that they get registered on GitHub and so that potential collaborators can see them Pull: when someone else is working on the same code and they have pushed their changes, your code is not the newest version anymore. To receive the newest version, you should do a pull