The Tech Lab by Aisha Ikram

 There are four ways of creating a Logic App. Azure Portal You have a visual designer available here where you can visually see the workflow and all the connectors, conditions, flow paths and available actions. Easy to create design the app and understand what is going on. You can not use source control or DevOps for this LA. Visual Studio 2019 You can design your app in Visual Studio using the building logic app Designer. Also you can also check in the logic app to the source control. Hence you can take the advantage of the DevOps features   Visual Studio Code You can manipula

Logic Apps are one of the compute solutions offered by Microsoft Azure. Logic Apps are design first workflows hosted in Azure in a serverless mode and implemented through underlying Azure Service Fabric. They have a visual design to connect your applications, components, services and APIs together in a workflow which is triggered by some event. As Logic Apps are executed in a serverless mode, so you are charged for the consumption plan price which is pay per execution. Logic Apps are used to integrate systems hence they are also called integration service. Components of Logic App Logic Apps require following: Trigger (Only One)  of any supported types (HTTP or other triggers (check list of supported triggers on Microsoft website) to trigger the execution Conditions/loops  (outcome from triggers is checked against a condition or put in a loop) based on which different Actions are executed Actions   are tasks which are

I will keep adding more links in the list below and categorise them according to 4 major categories of AZ-204 Exam so keep checking for the updates "Develop for the Azure Cloud" Sample Projects 50% of this exam falls in the "Develop for the Cloud" objective, and requires exposure to code. A collection of sample code you can play around with using Visual Studio 2019 or Visual Studio Code: Azure Batch Hello World - https://github.com/Azure-Samples/azure-batch-samples/blob/master/CSharp/GettingStarted/01_HelloWorld Azure Batch AI Code Samples - https://azure.microsoft.com/en-us/resources/samples/?service=batch-ai&sort=0 Service Bus Queue - https://github.com/Azure/azure-service-bus-dotnet Service Bus Code Samples - https://azure.microsoft.com/en-us/resources/samples/?service=service-bus&sort=0 Event Hubs - https://github.com/azure/azure-event-hubs-dotnet Azure Relay Hybrid Connections - https://github.com/azure/azure-relay-dotnet Event Grid Publish/Consume Eve

  Here is the list of learning path to prepare for AZ-204 Developing for Microsoft Azure exam from my personal experience. First foremost, subscribe to free Azure plan for portal, this will give you free access for some services for 30 days and for others 12 months access. you can browse through Azure portal and see its services. Exam expects 2 years experience of MS Azure, but if you just starting and want to go ahead with learning, you need to start from somewhere and this should be your first step. Take a Udemy course if you can buy one, go through all modules once. For absolute beginner, this is good step as the good instructor will quickly guide you through all the steps/services and give you a general idea of the content. However these courses are never comprehensive. you should go through them again and again if you are beginner or don’t have enough knowledge about a certain topic. you might want to go through

Data annotation can be used most commonly in in ASP.NET Core MVC or ASP.Net Data controls to perform model validation. Data annotations (available as part of the System. ComponentModel. DataAnnotations namespace, are attributes that can be applied to classes or class members to specify the relationship between classes, describe how the data is to be displayed in the UI, and specify validation rules. This article briefly tells you about data annotations, why they are useful, and how to use them in our .NET Core applications.  Types of Data Annotations  DA attributes are used to specify metadata on a class or a property. The data annotation attributes can broadly be classified into the following:   Validation attribute — Used to enforce validation rules on the properties of the entities  Display attribute — Used to specify how the data should be displayed in the user interface  Modeling attribute — Used to specify the r