Azure DevOps Full Course in 9 Hours [2026] | Azure DevOps Tutorial For Beginners | Edureka Live

Key Takeaways

Hello everyone and welcome to the Azure DevOps full course. Your step-by-step guide to mastering DevOps practices with Microsoft Azure. In this course, you will learn how to automate software development processes, manage infrastructure, and deliver application faster and more reliably using Azure's robust DevOps tools. You will get hands-on experience with services like Azure pipelines, repos, boards, and test plans and understand how to implement continuous integration, continuous delivery, and version control. The course will also cover best practices for collaboration, monitoring, and managing cloud resources effectively. And by the end, you will be ready to apply Azure DevOps solutions in real world projects and drive success in your organization. So before we begin, please like, share and subscribe to Idureka's YouTube channel and hit the bell icon to stay updated on the latest tech content from Idureka. Also check out Idureka's Microsoft Azure DevOps certification a 400 course. It is designed by experts to meet current industry standards. This comprehensive training prepares you for the Microsoft certified DevOps engineer expert certification. You will gain hands-on skills in designing and implementing DevOps strategies including collaboration, source control, security, compliance, continuous integration, continuous delivery and monitoring. Join now and take the next step toward becoming a certified Azure DevOps professional. So check out the course link given in the description box below. So first let us start by understanding what Azure DevOps is. >> Let us understand what is Azure DevOps. Now, Azure DevOps provides developer services for support teams to plan work, collaborate on code development, and build and deploy applications. Azure DevOps supports a culture and set of processes that bring developers and project managers and contributors together to complete software development. It allows organizations to create and improve products at a very fast pace than they can with traditional software development approaches like the waterfall approach. You can now work in the cloud using Azure DevOps services or on premises using Azure DevOps server. So you have two options now. Azure DevOps provides integrated features that you can access through your web browser or IDE client. Now you can use one or more of the following standalone services based on your business needs. The first one that we'll be talking about is Azure repos which provides git repositories or team foundation version control for source control of your code. Azure pipelines on the other hand provides build and release services to support continuous integration and delivery of your applications. Azure boards delivers a suite of agile tools to support planning and tracking work code defects and issues using canban and scrum methods. Azure test plans on the other hand provides several tools to test your applications including manual or exploratory testing and continuous testing. The last component is Azure artifacts which allows teams to share packages such as Maven, npm, Nug get and more from public and private sources and integrate package sharing into your pipelines. Now that we know what is DevOps and Azure DevOps, let's understand how to implement continuous integration. Before that we have to understand what is Azure pipelines. This is really important. Now, Azure Pipelines automatically builds and tests code projects to make them available to others. That's all it does. So, it works with just about any language. It could be Java, Python or project type. And these pipelines combines continuous integration and continuous delivery to constantly and consistently test and build your code and ship it to any target eventually. Now, you must be wondering what is continuous integration? Continuous integration is the practice used by development teams to automate the merging and testing of code. Implementing continuous integration helps to catch bugs way early in the development cycle which makes them less expensive to fix. Automated tests execute as part of the continuous integration process to ensure quality. Artifacts are produced from continuous integration systems and fed to release processes to drive frequent deployments. The build service in TFS helps you set up and manage continuous integration for your applications. Now continuous delivery on the other hand is a process by which code is built, tested and deployed to one or more test and production environments. Deploying and testing in multiple environments drives quality. So continuous integration systems produce the deployable artifacts including infrastructure and applications. Automated release processes consume these artifacts to release new versions and fixes to existing systems. Monitoring and alerting systems run continually to drive visibility into the entire continuous delivery process. The release service in TFS helps you set up and manage continuous delivery for your applications. Azure also has continuous testing on premises or in the cloud which is the use of automated build deploy test workflows and with the choice of technologies and frameworks that test your changes continuously in a fast scalable and efficient manner. Implementing CI/CD pipelines helps to ensure consistent and quality code that's readily available to users and Azure pipelines provides a quick, easy and safe way to automate building your projects and making them available to users. The next question that arises is why should one use Azure pipelines? Right? So the first and the most important benefit of using Azure pipelines is it works with any language, any platform. That's one of the biggest advantage. And the next advantage is that it deploys to different types of targets the same time. It also integrates with Azure deployments. It builds on Windows, Linux or Mac machines that is it works on any OS and it also integrates with the biggest and the most popular code hosting website that is GitHub. It also works with open-source projects. So, so this is definitely why one should opt for Azure to create their pipelines. Now let's move on and learn the differences between continuous integration and continuous delivery. Azure pipeline supports continuous integration and continuous delivery to constantly and consistently test and build your code and ship it to any target. Now you accomplish this by defining a pipeline. You define pipelines using the YML syntax or through the user interface. That is the classic way. Continuous integration. So in continuous integration, the tests are automated and builds for your project. Continuous integration also helps to catch bugs or issues early in the development cycle when they're easier and faster to fix. Items known as artifacts are produced from continuous integration systems. They're used by continuous delivery release pipelines to drive automatic deployments. Continuous delivery, on the other hand, automatically deploys and tests code in multiple stages to help drive quality. Continuous integration systems produce deployable artifacts which include infrastructure and applications. Automated release pipelines consume these artifacts to release new versions and fixes to the target of your choice. Now that we know the difference between continuous integration and continuous delivery. Let's move ahead and learn how to create Azure pipelines. So the first way to create Azure pipelines is to define pipelines using YML syntax. You define your pipeline in a YML file called Azure pipelines yimml with the rest of your application. The pipeline is versionized with your code and it follows the same branching structure. So you can get a validation of your changes through code reviews in pull requests and branch build policies. Every branch you use can modify the build policy by modifying the Azure pipelines.l file. A change to the build process might cause and break or result in an unexpected outcome. So be careful and this occurs because the change is in version control with the rest of your code base and you can easily identify the issue. So the first step is to configure Azure pipelines to use your git repository where you're going to edit your code where you're going to really write where you're going to really store your entire project and then you're going to edit your Azure pipelines.l file to define your build. In the third step, you're going to push your code to your version control repository. And this action finally kicks off the default trigger to build and deploy and then eventually monitor your results. So once the pipeline has been created, your code has been now updated, built, tested, and packaged. It can then be deployed to any target that you'd like. There's also another way to create your Azure pipelines. That is to define pipelines using the classic interface. Now here you create and configure pipelines in the Azure DevOps web portal with a classic user interface editor. So what you do is you define a build pipeline to build and test your code and then to publish artifacts. You also define a release pipeline to consume and deploy those artifacts to deployment targets. So here the first step is to configure Azure pipelines to use your git repository. Then you use the Azure pipelines classic editor to create and configure your build and release pipelines. Then you finally push your code to your version control repository. This action triggers your pipeline and runs tasks such as building or testing codes. The build creates an artifact that's used by the rest of your pipeline to run tasks such as deploying to staging or even production. So the tasks that are released is termed as continuous delivery. And the part where you're building tasks and testing them is termed as continuous integration. Now that we know how to create your own Azure pipelines, let's go ahead and learn to set up release management workflow. So the first thing that we're going to learn is how to design a release strategy. So we have to understand what is release pipelines. Okay. So release pipelines enable teams to continuously deploy their application across different stages with lower risk and with faster pace. Deployments to each stage can be fully automated by using jobs and tasks. Teams can also take advantage of the approvals and gates feature to control the workflow of the deployment pipeline. Here, each stage in a release pipeline can be configured with pre-eployment and post- deployment conditions that can include waiting for users to manually approve or reject deployments and checking with other automated systems that specific conditions are met. In addition, teams can configure manual validations to pause the deployment pipeline and prompt users to carry out manual tasks, then resume or reject the deployment by using gates, approvals, and manual intervention. You can take full control of your releases to meet a wide range of deployment requirements. You can also release deployment control using gates. Gates allow automatic collection of health signals from external services and then promote the release when all the signals are successful at the same time or stop the deployment on timeout. Typically gates are used in connection with incident management, problem management, change management, monitoring and external approval systems. Some scenarios and use cases for gates are incident and issue management. Here you ensure the required status for work items, incidents and issues occur regularly. For example, now you have to ensure deployment occurs only if no priority zero bugs exist and validation that there are no active incidents take place after deployment. Also another scenario would be to seek approvals outside Azure pipelines. here. Notify non-asure pipeline users such as legal approval departments, auditors or IT managers about a deployment by integrating with approval collaboration systems such as Microsoft Teams or Slack and waiting for the approval to complete. In another scenario, there could be quality validation query metrics from tests on the build artifacts such as pass rate or code coverage and deploy only if they are within a required threshold. There are many other use cases like security scan on artifacts, user experience relative to baseline change management, infrastructure health. There are many scenarios that you can use gates for. So this is a really important topic. Moving on, let us learn how to implement compliance and security. Firstly, we will have to design a dependent management strategy. Before we learn how to design one, we will have to understand what is dependency management. Now, with modern software architectures and development methods, software dependencies can come intertwined quickly with more online repositories like GitHub, DockerHub, pre-built libraries and services can be easily published and leveraged. Now these projects can be managed by all sorts of individuals or groups and have a very wide range of work ethics from well-maintained solutions with good community and multiple contributors and release schedules that is all the way to the other end of the spectrum. Code is also developed internally and is often reused. Wherever the source comes from the problem is the same. Once implemented one project now has a dependency on other. Now for example when a team comes together to build a solution they may decide for various reasons to leverage code that already exists. Now depending on the type and language used for that particular project there are different sources that can be leveraged to accelerate development. For example, let's say you're running a net application that's going to be processing JSON that you retrieve from Azure to describe Azure resources. Now, rather than having to write all the logic to handle the JSON file, your team decides to leverage a popular package called Newtons.json, which is a publicly available package. You could leverage the Nougat package that's already been built and published for consumption. By leveraging this package in your code, you have created a dependency on the package for your solution. Now, you must be wondering what is a package? A package is simply a standardized way of distributing codes that can be consumed by another application or solution. Metadata is used to help store and version and identify these packages. So there are different types of packages, right? So these artifacts can be Nug, npm, they can also be Maven and all of these are part of the packages. Okay, so we'll be talking about Nugat. So, Nougat is a free open-source package manager designed for the Microsoft development platform used innet since its introduction in 2010. Nougat has evolved into a larger ecosystem of tools and services. So, it is distributed as a visual studio extension. The Nougat packet has a nupg suffix and as a zip file with a specific folder structure. Maven packages on the other hand are often used for Java projects. Maven can also be used to build and manage projects written in C, Ruby, Scala and other languages. Now a project object model file describing the metadata of the project is also stored within this package. npm on the other hand is a package manager for JavaScript programming language and it's primarily used for runtime environments with Node.js and npm package contains a package.json file describing the metadata of that package. The Python package index is a repository of software for the Python programming language. Python's packaging is built for distributing reusable code called libraries between developers. Now these packages are libraries used as building blocks to create applications and have a tar.gz extension. Azure DevOps also has the ability to store universal packages. A universal package installed one or more files together in a single package that have a name and version which is useful for many ad hoc situations where you want diversion and track files. Containerized workloads are becoming more popular as platforms like Kubernetes are becoming mainstream. We'll be talking about Kubernetes later on in the session. Docker images on the other hand are generally complete self-contained system. Azure artifacts are available in Azure DevOps DevOps servers as well as in team foundation server 2017 and 2018. The sources allow you to integrate packages seamlessly into your CI/CD pipeline. Now there are three concepts you need to understand when managing these Azure artifacts that we just talked about that is feeds, views and upstream sources. Feeds are the primary method for delivering packages. Microsoft really recommends one feed per project and to achieve this we can utilize the feature of upstream sources which allows you to combine multiple sources into a single feed. Now using this method allows you to control sources in your project in the various levels of access. Here we see two options we have when adding upstream sources. A public source and from an existing Azure artifacts feed from within your Azure DevOps organization. When adding a public source, the only supported package type is an npm source which we've already talked about. Now, when you're adding a source from within your Azure DevOps organization, you can target an Azure artifacts feed. This allows you to use different package types that is Nugat, Python, and Maven. You can scope the visibility of your package feed to your organization, which is multiple projects. And this is by default. Now, a benefit of bringing all these packages together in one feed is the copies are made of the sources. Now if you're using sources and those sources goes offline, you'll be able to maintain your own version of this packet. Upstream sources on the other hand enable you to manage your products dependencies in a single place. Using upstream sources makes it easy to use common packages in your solution. It has the added benefit and gives you protection against outages and corrupted or compromised packages from upstream sources and also as a copy of the packages stored locally. Now let's move on and understand how to manage security and compliance. Whites source bold is a lightweight open-source security and management solution integrated within Microsoft's Azure DevOps services and Azure DevOps server formally that is TFS products. It enables you to do many things like detect and remedy vulnerable open-source components. Also, you can generate comprehensive open-source inventory reports per project or build. You can also enforce open-source license compilence, including dependencies, licenses, and also you can identify outdated open-source libraries with recommendations to update. This is just one solution to manage security and compliance. Let's move on and understand how to implement continuous feedback. So, you can design system feedback mechanisms. The first one is to use application insights metric dashboards. Now, application insights has always provided a summary overview pane to allow quick at a glance assessment of your application's health and performance. The new overview dashboard provides a faster, more flexible experience. Dashboards are basically customizable interactive signboards that provide real-time information. Dashboards are associated with the team or a project and display configurable charts and widgets. Charts on the other hand are query based status or trend charts derived from a work item, query or test results. Widgets on the other hand display configurable information and charts on dashboards. The widget catalog provides brief descriptions of those widgets available to you. Now in addition, you can add widgets provided through the Azure DevOps marketplace. In context, reports are system generated charts that support specific services. Examples are team velocity, sprint burndown, and the cumulative flow diagram. These reports are displayed on the analytics tab for a specific service and derive data from analytics. PowerBI reports allow users to create rich customized PowerBI reports or other reports using O data queries of analytics data and the return JSON data. If you see the fourth point, you can also configure a burndown or burn up widget. The burndown and burn up widgets provide the flexibility to create charts for any type of scope, any number of teams and within specified time periods. Burndown charts focus on remaining work within a specified time period while burnup charts focus on completed work. Then the last point, both lead time and cycle time widgets are extremely useful to teams as they indicate how long it takes for work to flow through their development pipeline. Lead time measures the total time elapsed from the creation of work items to their completion. Cycle time on the other hand measures the time it takes for your team to complete work items once they begin actively working on them. Moving on, let us understand how to optimize feedback mechanisms. So the application life cycle doesn't finish with application deployment. Feedback is a very important element of refining an application. Whether that's exception detection and diagnosis or improving the user experience. You can do this in various ways. You can analyze alerts to establish a baseline. You can analyze telemetry to establish a baseline. You can also perform life site reviews and you can also perform ongoing tuning to reduce non-actionable alerts. Moving on to the next part of the session, we'll be talking about some of the Azure tools. The first one that we're going to talk about is Azure Kubernetes Service, which simplifies deploying a managed Kubernetes cluster in Azure by offloading much of the complexity and operational overhead to Azure. Now, as a hosted Kubernetes service, Azure handles critical tasks for you like health monitoring and maintenance. Since the Kubernetes masters are managed by Azure, you only manage and maintain the agent nodes. Thus, a managed Kubernetes service AKS is free. You only pay for the agent nodes within your clusters and not for the masters. You can create an AKS cluster using the Azure portal, the Azure CLI, Azure PowerShell or even using template-driven deployment options such as resource manager templates and terraform. Now when you deploy an AKS cluster, the Kubernetes master and all nodes are deployed and configured for you. Additional features such as advanced networking, Azure active directory integration and monitoring can also be configured during the deployment process. Windows server containers are also supported in AKS. Now there are some technologies used for configuration management like ARM templates, Terraform, Chef Puppet Anible. ARM templates are a way to declare the objects you want, the types, names, and properties in a JSON file which can be checked into source control and managed like any other code file. ARM templates are what really gives us the ability to roll out Azure infrastructure is code. Also, there is Terraform which is an open-source tool for provisioning and managing cloud infrastructure. It codifies infrastructure in configuration files that describe the topology of cloud resources. Now these resources include virtual machines, storage accounts and networking interfaces. The Terraform CLI provides a simple mechanism to deploy and version the configuration files to Azure. Supported by Chef, the Chef automate Azure marketplace solution enables you to build, deploy, and manage your infrastructure and applications collaboratively. Moving on to the last part of the session, we have a case study for you. So we'll be talking about how Service Now want to make work easier and more efficient for their customers through its software as a service workflow platform. Now to maximize the value it can deliver, Service Now moved its business critical SAP estate including 50 essential applications, more than 10 SAP landscapes, 50 database instances and over 50 terabytes of storage and other IT assets to Microsoft Azure. Service Now relies on the high level of security that Azure provides along with the scalability and agility that a rapidly growing company needs to expand. Benefits of the migration include an 80% reduction in deployment cycle time and improved service level agreement, better disaster protection, improved SAP application performance, and a 40% reduction in TCO. Service Now helps some of the world's largest and most influential companies work better. It also helps customers in numerous industries reduce cost, increase productivity, streamline processes, and accelerate digital transformation. It does this by delivering a comprehensive software as a service digital workflow platform with native AI capabilities and intuitive user experience. To support its customers, Service Now must ensure that its own internal systems and processes are powerful, dependable, and scalable. The company has long relied on Azure to keep its operations running. [Music] Let's get started with the video. Let's kick things off by talking about why businesses and everybody for that matter need cloud computing. Here's an example. Meet John, who is an entrepreneur who has a brilliant idea for an app which solves a problem and has a great user experience. So what does John need? John will need developers to build his app. But other than that in terms of infrastructure, he will need servers. Then he will need storage devices, a dedicated network, security systems, and of course he will need a dedicated IT operations team to monitor the whole infrastructure and make sure everything is working properly. John figured that there would be four major problems with this setup. And what are those? Let's take a look. So the first problem is that owning his own infrastructure would require a huge amount of money and because of a huge investment in setup of the infrastructure this would also greatly increase the risk if the app fails. Second problem is that he noticed that the infrastructure would take too long to set up as he would have to buy all the components required for his infrastructure. Then hire IT technicians to install all the components and connect everything up so that everything is talking to each other and working nicely. So that means more money and more time. Next, he realized that even after the expensive setup of the infrastructure, he would have to hire a team of IT operations to work around the clock for the upkeep of the infrastructure. This would include things like resolving issues with the hardware or software, replacing broken pieces of the infrastructure so he would need to have spare parts on hand, switching to backup servers if the server goes down, preventative maintenance and so on means more money and more headaches when the issues crop up. Another problem has to do with the inability of the infrastructure to scale. So what if the traffic on the servers increases or decreases abruptly? Well, if the traffic increases, he will have to scale the infrastructure to meet that demand, which means expanding the infrastructure. So, buying more components, probably renting more office spaces, hiring more IT staff to monitor the expanded infrastructure, and so on. But what if there's a sudden drop in the demand? All of this extra infrastructure and resources will sit idle. What about the extra people he hired? He will have to let them go. Well, it's terrible, but he may have to. Well, now let me tell you John was smart. He did not opt for this setup. He opted for cloud computing because he was studying up on cloud computing and he found that all big and small companies that are at the top in their domains are using cloud computing and this research into cloud computing was a real eye opener as he found that all these issues that he would face with the infrastructure that we just talked about could be solved by using the cloud. So obviously he opted for cloud. This is because there was almost no initial setup cost required and it could be done in a few minutes or hours by using a single computer and he wouldn't need a dedicated team to take care of the physical machines because that is taken care of by the cloud provider. And finally to John's relief, infrastructure in the cloud scales automatically as the demand changes. Isn't that freaking amazing? So why don't we find out more about cloud computing in this next section. What is cloud computing? Cloud computing is the delivery of the computing services like servers, storage, databases, networking, software, analytics, intelligence and so on over the internet which we call colloally the cloud. Okay. So let's understand that John takes a computer that is connected to the internet. Then he accesses the resources on cloud platform. So these resources that John needs are running on physical machines in the data center that are owned by cloud providers. So like I said before, all John needs is a computer that is connected to the internet and the remainder of the infrastructure is actually provided by the cloud provider and he can access the resources that he needs from the data center using the cloud platform. So how does this work? Well, first John goes to the cloud provider whichever one he likes the most. Amazon Web Services, Microsoft Azure, Google Cloud, these are the top cloud providers. So after going to the cloud provers website, he signs up for an account and then he signs up for the services as per his requirements and configures the resources that he will need for the app to run on. And the amazing thing is that he only pays for the services that he uses and for the amount of time that the services were up for. Isn't that amazing? Of course it is. So let's now talk about what is Azure. Azure is a cloud platform that is provided by the company Microsoft from which you can rent your resources and services. So you can grab a computer that is connected to internet then go to Azure portal on your web browser and then access the resources that you need by signing up with Microsoft Azure. So now it's time to find out which cloud platform did John choose. It's kind of a no-brainer, but here's what John says. The developers of my app and I we all use Windows OS and other Microsoft products. So we wanted a cloud service that is best compatible with them. Can you guess which one this is? Of course it is Microsoft Azure because it is most compatible with the Microsoft products. So before we talk about the services, why don't we find out some of the interesting things about Azure. Just like every other cloud platform, Azure provides five distinct type of services. Infrastructure as a service, platform as a service, software as a service, container as a service, and functions as a service. Apart from that, Azure has 22 main categories of products which we will take a look at later on. Next, Azure is operating globally in 60 plus regions and provides its services to 140 countries and counting. So, just like the major cloud platforms, Azure provides pay as you go plans and free plan. So, there are actually no upfront fees for signing up with Azure and you can pay as you go and only pay for the time your services are running. And just like every other cloud platform, Azure provides free basic plan which is surprisingly good and it is valid for 12 months. So you can tinker around and see if you like it. Okay. So what about the languages that are supported on Microsoft Azure? They are C, F, Java, TypeScript and Python. Now let's move on to the next section where we discuss the services offered on Azure. So in the previous section you probably remember that I mentioned that Azure has 22 categories of products but what I did not mention is that it has over 600 services. So obviously we are not going to be able to have enough time to discuss all 600 services. So here's your homework. Go to Azure's website and check out each of these categories and read up on them. If you have any questions, come back to this video and comment down in the section and we will be more than happy to answer any of those for you. So, I hope that you got a picture of all the categories of services provided by Microsoft Azure. So, let's now go back to John. John needed three services. They were compute, networking, and storage. So, let's take a look at each one of these in a little bit of a detail and then move on. So the first product that he's going to need to build his infrastructure in the cloud is compute. He can use this to deploy and manage virtual machines, containers, and batch jobs as well as support remote application access. Compute resources created within the cloud can be configured with either public IP addresses or private IP addresses depending on whether the resource needs to be accessible to the outside world. So some of the services that are offered within compute product are virtual machine, containers, kubernetes service, cloud services, mobile apps. Let's move on to talk about the next which is networking. So after setting up the virtual machines using the compute product, he will require to connect those virtual machines up so they can talk to each other and form a network. So this product gives you the ability to set up virtual networks, dedicated connections and gateways and it also gives you services for traffic management and diagnosis, load balancing, DNS hosting and network protection against some of the attacks like DDoS. Next one that John needs is storage obviously for his virtual machines so that they can store customer data and use backup storage for all of the infrastructure. So there are various services that are offered within storage like Azure disc storage, blob storage, Azure backup, Q storage and many more. This category of services provides scalable cloud storage for structured and unstructured data. It also supports big data projects, persistent storage and archival storage. Similarly, there are 19 more categories that provide services that can cater to all needs of any organization or company, which brings us to our next section, which is companies using Azure. Let's see which companies use Azure. So, hundreds of big companies use Azure, but these are the ones that I picked for you guys because each one of these use Azure for a different purpose. So, let's check that out. eBay has been using Azure for app development and hosting since 2010, which is the same year Microsoft announced Azure to the world. Boeing mainly uses Azure for its data analytics services for things like crew planning, maintenance optimization, fuel optimization, and crew training by building predictive models on the platform. BMW uses Azure's Internet of Things to make manufacturing process within their factories more efficient by connecting all different machines, sensors, and other devices. On the other hand, Samsung has used Azure for its smart TV infrastructure. The entire smart TV infrastructure is actually on the Azure platform. By choosing Azure, Samsung was able to achieve a significant reduction in costs and increased capacity in order to meet its rapidly growing customer base. Now let us understand what is Azure certification. Azure certification is a level of Microsoft cloud expertise that an individual obtains by passing one or more certification exams. Microsoft Azour certification validates an individual cloud expertise and skills. Now let us move on to our next topic and see some of the benefits of Azure certification. With an Azure certification, you validate your cloud skills in your selected domain. You will earn the credibility and your present or your future employee will know for sure that you have worked on Azure and have the skill as you mentioned. The next advantage is you'll have higher salary packages. Business wire has estimated that Azure course certification have raised their wages by 20 to 40%. payscale.com also announced that based on the position and job description, those credited by Microsoft Azure could get a salary of $128,000 peranom. With the Azure certification, you can pursue a wide range of career options. You can become a cloud architect, a developer or solution architect or even AI engineer. There are many options and in addition to this, the certification enables you to work with different industry at different locations. The next advantage would be it provides a proof of commitment. To get an Azour certification, you should be able to commit yourself to it. You would have to sign up for a course, study, and then only pass the exam. That would imply that you can commit your time and resources towards achieving your goal and that you're dedicated to improving your career objectives in the long term. These were some of the benefits of Azure certification. Now, let us move on to our next topic and see what are the types of Azure certification. First we'll take a look at different Azure certification based on job roles. So first we have developer certification who designs build and test cloud solutions. Second is system administrator who implements monitors and maintains Microsoft solution. Third is solution architect who expertise in compute network and security. Fourth we have the data engineer who designs and implement the management monitoring security and privacy of data using the full stack of data services. Fifth is data scientist who applies machine learning techniques to train, evaluate and deploy that sol business problems. And then sixth we have the AI engineer who use cognitive services, machine learning, knowledge mining to architect and implement Microsoft AI solutions. On seventh we have DevOps engineer who combines people, process and technologies to continuously deliver valuable products and services to the implements security controlction. He also manage access and protects data application and network. We have the functional consultant who leverages Microsoft Dynamics 360 Microsoft to anticipate and plan for customer needs. Microsoft Azure certification have four level of certification. Fmental level, second is the associate level, third is expert and we have specialtity. Now speciality certification is a certification based on a particular domain. Now let us move on to our next topic and see some of the major job role based certification. Now before we get into any major role-based certification, I would like to talk about a fundamental certification which is Microsoft certified Azure fundamentals or a900. Now this certification is intended for candidates who are just beginning to work with cloud-based solution and services or who are new to Azure platform. This certification will provide an opportunity to prove your knowledge of cloud's concepts, Azure services, Azure workloads, security and privacy in Azure as well as Azure pricing and support. Candidate who take the certification should be familiar with general technology concepts including concepts of networking, storage, compute, application support and application development. The AZ900 certification is a fundamental certification which can be used to prepare for any other Azure role-based or specialtity certification but it is not a prerequisites for any of them. Now let us see some of the major role-based Azure certification. We have the Azure administrator associate or A 104. Candidates for the Azure administrator association should have subject matter expertise in implementing, managing and monitoring an organization's Microsoft Azure environment. The responsibility include implementing, managing and monitoring the identity, governance, storage, compute and virtual network in a cloud environment. They also have to monitor and adjust resources wherever and whenever needed. They often serve as a part of larger team dedicated to implementing an organization's cloud infrastructure. For this certification, a candidate should have at least 6 months of hands-on experience administrating Azure. Along with that, they should also have strong understanding of core Azure services, Azure workloads, security and governance. The next certification is Azure Developer Associate or A244. Candidate for the Azure Developer Associate Certification should have subject matter expertise in designing, building, testing and maintaining cloud application and services on Microsoft. The responsibilities include participants of cloud development from requirements definition and design to development, deployment and maintenance to performance tuning and monitoring. Azure developers should participate with cloud solution architect, cloud administrator and clients to implement solutions. A candidate appearing for this certification should have at least one or two years professional development experience and experience with Microsoft Azure. Next, we have an expert level certification which is Azure solutions architect expert or a3 or 3.4. Candidates for the Azure solution architect expert certification should have subject matter expertise in designing and implementing solution that run on Microsoft Azure which would include aspects like compute, network, storage and security. The responsibilities include advising stakeholders and also translating business requirements into secure, scalable and reliable cloud solutions. They should partner with cloud administrator, cloud DBAs and clients to implement solutions. A candidate appearing for the certification should have advanced experience and knowledge of IT operation and also know how decision in each area affects an overall solution. These were some of the major role-based certification. Now let us move on to our next topic and see an overview of the exam guide. First we have the exam format or question types. Microsoft continuously introduces innovating testing technologies and question types. Your exam might contain questions like multiple choices, repeated answer choices, short answers, mark review, drag and drop labs and so on. The time limit for different examination is for associate and expert job ro exams you have 130 minutes to complete it. For job ro fundamental exams you have 60 minutes to complete it. For associate and expert job role exam that contains lab you have 150 minutes to complete it. Now talking about the cost for the exam for the fundamental exam it would cost you $99. For the associate and the expert level exams, the cost is $165 and you can write the certification exams in either English, Chinese, Korean or Japanese. Now the fundamental certification can also be written in Spanish, German or French. Now let us move on to a last and important topic which is how can you prepare for the certification. First start with the basics. So if you're not 100% sure which certification to start with, I would recommend you to start small by taking the A900 Azure fundamental certification exam. This will help you understand how Microsoft exam work by not being too deep into technologies. And after you have experienced taking the Microsoft exam, this will help you understand how Microsoft exam work while not being too deep into the technology. having experience taking the Microsoft exam. It will also help you focus on the actual topic and not on the testing process. The next step is to understand the exam content. The first thing to do after you decide which exam you're going to write is to see what you're asked during the exam. Every Microsoft exam page has the skill measured in the exam. This list is very accurate and helps you focus and study the right content. The page will also have some training and courses to prepare for the exam. You should also understand the different question types asked in the exam which will help you in the certification. The next step is to take hands-on learning courses on Microsoft learn for free. Microsoft learn is a free learning platform for a lot of different Microsoft technologies. It provides you with various learning paths depending on your job roles or the skills you're looking for. Most of the learning paths gives you hands-on learning opportunity so that you can develop practical skills through interactive training. The next and the most important step is hands-on experience. The best way to learn and pass the Microsoft Azure exams is by having real hands-on experience working with the technology. While Microsoft learn gives you some free hands-on learning modules, there is also Azure free account. The Azure free account will provide you with 12 months of free Azure services. So you can work on various Azure services for free. Now the next step which will help you prepare for the certification is reading the Microsoft documentation. It will help you understand the topic better which might appear in the exam. As I've mentioned before, read the skills measured on the exam page. Look up for the specific Microsoft documentation pages and read through them and then try them out in the tutorials. You can also refer some books for Microsoft press. You can find Microsoft Azure documentation and Microsoft press in Microsoft Azure certification official page. After this step, you can also take up a practice exam. Some of the Azure certification have practice examination along with it which is very similar to the actual certification examination. Now let us understand what you'll get after you sign up for Azure free account. So basically you get many things for one year which includes $200 credits for first 30 days, popular services free for 12 months, more than 40 other services which are free all the time and 750 hours of virtual machines which includes Windows and Linux and you can create up to 250GB SQL database. Apart from this, you can get other services like free dev test labs, free load balancers, free batch jobs, free SQL server, etera. Now we'll see how to create an Azure free account. For this, you require a phone number, a credit card, a GitHub or a Microsoft account to create your Azure free account. The best way is you can create a Hotmail or Outlook email ID. then then you can use the same email ID and password to sign up for the Azure free account. So firstly you need to sign in through the Microsoft account using your outlook outmail or any ID and after that you need to follow the couple of steps that is you need to first fill out about you and then you'll go through a verification by phone and then you go through the verification by card and finally you sign up. In the first step that is about you. Here you fill up your basic details that is first name, last name, email id and phone number. Then followed by next step that is identity verification by phone. So here you give your phone number and you will receive an OTP and you need to just like type your one type password and just verify your phone number. So once you verified you move on to the next step that is identity verification by card. Here you fill up your all credit card details followed by card hold number then credit card number it's expiry and CV and your address. Once all it is done then they charge you around 2 rupees just for your verification. They charge you 2 rupees and it is deducted. Once it is deducted you move to the next step that is like accepting the agreements. So you need to just stick all the agreements and finally you sign up. So once all this process is done then you are ready to start with Azure. So this is how you create your Azure free account. It's very simple and super easy. So now let us know how to create an Azure free account without a credit card. So can we do this? So the answer is yes. Yes you can. You can create an Azure free account without a credit card. But for this you need to have an a school account or a required school email id. So you basically log in as a student. In this case, if you log in through a student account, so you will receive only 100 credit points and you also get various other services like 750 hours Windows virtual machine and you can create up to 250GB SQL database and um you also get machine learning free workspaces, SQL server developer edition that is also for free and lots of AI and machine learning features. This is how you create your Azure free account without a credit card. Now let's move on to the next topic that is can we delete a credit card. So many of us had a doubt that can we actually delete our credit card. So here in this picture you could see that I have a payment method and here the delete option is disabled. So why is this so? In this case, you cannot delete a credit card as it is there is only one payment method option. If you really want to delete a credit card detail, then you need to add one more payment method. So, you can click onto this add icon and you can add your new payment method. Once the payment method is added, then your delete option gets enabled. Then after that, you get the access to delete any one of your credit card details. So this is how you delete a credit card detail. Next, how to cancel subscription. So it is very easy to cancel the Azure subscription. So for this you just need to go to cost management section. There you get go to subscription option. Once you click on to the go to subscription you get all the details of your current subscription. So and you can also find the cancel subscription option there. So once you click on to the cancel subscription they will ask you the type of subscription name and you need to provide a reason why are you canceling the subscription. So you just give the reason prescribed reason of your own and then just click on cancel subscription. So once you click on to the cancel subscription they will ask you the type of subscription and the reason why you want to cancel the subscription. So you can give your details accordingly and click on cancel subscription. So this is how you can cancel your Azure subscription. So let us just go ahead and take a look at what this Azure portal does. Before I start about Azure portal, I would like to inform you that we would be opening Azour's p