Setup Gitlab Continuous (CI/CD) on Azure
Deploy Ubuntu VM with Docker Engine Setup Gitlab on Ubuntu Deploy Webapp Setup Gitlab Continuous (CI/CD) Step-by-step video Deploy Ubuntu VM with Docker Engine Go to https://gitlab.com/daveRendon/ubuntu-vm-with-docker-engine/blob/master/README.md and deploy to Azure Provide the parameters for the VM and click purchase Once the VM is provisioned go to the VM configuration and change the IP Address to Static Connect to the VM using SSH Setup Gitlab Connect to the Ubuntu VM via SSH Install and configure the necessary dependencies sudo apt-get update sudo apt-get install -y curl openssh-server ca-certificates Install Postfix sudo apt-get install -y postfix During Postfix installation a configuration screen may appear. Select 'Internet Site' and press enter. Use your server's external DNS for 'mail name' and press enter. If additional screens appear, continue to press enter to accept the defaults Add the GitLab package repository curl https://packages.gitlab.com/install/repositories/gitlab/gitlab-ee/script.deb.sh | sudo bash Install the GitLab package. Change https://gitlab.example.comto the URL at which you want to access your GitLab instance. sudo EXTERNAL_URL="https://gitlab.example.com" apt-get install gitlab-ee Browse to the hostname and login using the default account's username root to login In this case> http://gitlabs.eastus.cloudapp.azure.com Deploy webapp on azure Deploy ARM Template using Azure Portal: https://gitlab.com/daveRendon/ifreeze/blob/master/webapp.js Create Gitlab project on Azure Access to Gitlab on Azure http://gitlabs.eastus.cloudapp.azure.com Create new project Generate your SSH Key https://gitlab.com/help/ssh/README#generating-a-new-ssh-key-pair Setup Gitlab Continuous (CI/CD) on Azure Go to the Azure web app Choose Deployment Center Select Source Control "External" and click Continue Now in Build Provider select "App Service Build Service" Add the Gitlab URL and the master branch In choose Private Repository "YES" and provide the credentials, in this case user root and the password previously created Test changes on the Gitlab project running on Azure Step-by-Step video https://youtu.be/naSdpfOuaUoAzure Training & Certification
Get the tools you need to advance your career with Microsoft Azure Expand your career opportunities in the cloud with three offers that combine training and industry-recognized Microsoft Certified Professional (MCP) certifications. Choose the tools that can help you to succeed—from free on-demand learning to Microsoft Azure certification to MCP exam prep and retake opportunities. Prove to the world and show employers that you’re ready to take advantage of the growing collection of integrated cloud services in Azure, as you gain the skills to develop solutions that can lower total cost and help improve scalability, security, and privacy. Choose the Azure certification training offer that best meets your needs: Free training Learn and build Azure skills Get full access to Azure massive open online courses (MOOCs) in the Microsoft training on Open edX catalog. Earn a free certificate of completion for each completed MOOC. Learn more at: https://aka.ms/azurefreetraining
Microsoft Azure Master Program
https://www.azuremaster.in/ The World Today is Cloud Ready, Are You? 4 reasons to join the Microsoft Azure Master Program: Learn with on-demand and instructor-led trainings; Become a cloud computing master with Microsoft Azure Certifications; Engage with your peers from the IT ecosystem from across the globe; and Get recognized as a Microsoft Azure Master. Start your cloud journey with Microsoft Azure today! https://www.azuremaster.in/register
Running Selenium Tests on Azure Virtual Machine
Goodday, We are using an Azure Virtual Machine to run our builds on, part of the build process is the run Selenium Tests on our web application, we have a requirement that forces us to use the Chrome driver. But the default screen resolution is 1024x768. Is there a way to increase the Virtual Machines default screen resolution, if so how would one achieve this? Regards, Dylan.Bad Gateway Error - SharePoint connector in Azure Logic Apps
We are using a SharePoint connector in Azure Logic Apps Designer. It supposed to work smoothly but recently noticed that all our existing apps failing the SharePoint connector. The "Bad Gateway" error appeared across 3 separate tenants (Issue is intact in all tenants). Used the workaround of “putting the folder/library link manually in the field” - Although this might work for triggers, it does not work for the SharePoint file create action. I get this error: { "status": 400, "message": "Library https://sitename.sharepoint.com/sites/Longwave/Automation/Calibre/CRMS does not exist in this site. Make sure that you pick an existing library to create your file or folder in.\r\nclientRequestId: 5a6b2dcd-d690-4f78-8c57-f65339ce0de8\r\nserviceRequestId: c23d4f9f-30c3-a000-f353-db1664632f34", "error": { "message": "Library https://sitename.sharepoint.com/sites/Longwave/Automation/Calibre/CRMS does not exist in this site. Make sure that you pick an existing library to create your file or folder in." }, "source": "sharepointonline-ae.azconn-ae.p.azurewebsites.net" } Nevertheless, SharePoint connector in PowerAutomate works well. Any insights are really appreciated !How to deploy n8n on Azure App Service and leverage the benefits provided by Azure.
Lately, n8n has been gaining serious traction in the automation world—and it’s easy to see why. With its open-source core, visual workflow builder, and endless integration capabilities, it has become a favorite for developers and tech teams looking to automate processes without being locked into a single vendor. Given all the buzz, I thought it would be the perfect time to share a practical way to run n8n on Microsoft Azure using App Service. Why? Because Azure offers a solid, scalable, and secure platform that makes deployment easy, while still giving you full control over your container and configurations. Whether you're building a quick demo or setting up a production-ready instance, Azure App Service brings a lot of advantages to the table—like simplified scaling, integrated monitoring, built-in security features, and seamless CI/CD support. In this post, I’ll walk you through how to get your own n8n instance up and running on Azure—from creating the resource group to setting up environment variables and deploying the container. If you're into low-code automation and cloud-native solutions, this is a great way to combine both worlds. The first step is to create our Resource Group (RG); in my case, I will name it "n8n-rg". Now we proceed to create the App Service. At this point, it's important to select the appropriate configuration depending on your needs—for example, whether or not you want to include a database. If you choose to include one, Azure will handle the connections for you, and you can select from various types. In my case, I will proceed without a database. Proceed to configure the instance details. First, select the instance name, the 'Publish' option, and the 'Operating System'. In this case, it is important to choose 'Publish: Container', set the operating system to Linux, and most importantly select the region closest to you or your clients. Service Plan configuration. Here, you should select the plan based on your specific needs. Keep in mind that we are using a PaaS offering, which means that underlying compute resources like CPU and RAM are still being utilized. Depending on the expected workload, you can choose the most appropriate plan. Secondly—and very importantly—consider the features offered by each tier, such as redundancy, backup, autoscaling, custom domains, etc. In my case, I will use the Basic B1 plan. In the Database section, we do not select any option. Remember that this will depend on your specific requirements. In the Container section, under 'Image Source', select 'Other container registries'. For production environments, I recommend using Azure Container Registry (ACR) and pulling the n8n image from there. Now we will configure the Docker Hub options. This step is related to the previous one, as the available options vary depending on the image source. In our case, we will use the public n8n image from Docker Hub, so we select 'Public' and proceed to fill in the required fields: the first being the server, and the second the image name. This step is very important—use the exact same values to avoid issues. In the Networking section, we will select the values as shown in the image. This configuration will depend on your specific use case—particularly whether to enable Virtual Network (VNet) integration or not. VNet integration is typically used when the App Service needs to securely communicate with private resources (such as databases, APIs, or services) that reside within an Azure Virtual Network. Since this is a demo environment, we will leave the default settings without enabling VNet integration. In the 'Monitoring and Security' section, it is essential to enable these features to ensure traceability, observability, and additional security layers. This is considered a minimum requirement in production environments. At the very least, make sure to enable Application Insights by selecting 'Yes'. Finally, click on 'Create' and wait for the deployment process to complete. Now we will 'stop' our Web App, as we need to make some preliminary modifications. To do this, go to the main overview page of the Web App and click on 'Stop'. In the same Web App overview page, navigate through the left-hand panel to the 'Settings' section. Once there, click on it and select 'Environment Variables'. Environment variables are key-value pairs used to configure the behavior of your application without changing the source code. In the case of n8n, they are essential for defining authentication, webhook behavior, port configuration, timezone settings, and more. Environment variables within Azure specifically in Web Apps function the same way as they do outside of Azure. They allow you to configure your application's behavior without modifying the source code. In this case, we will add the following variables required for n8n to operate properly. Note: The variable APP_SERVICE_STORAGE should only be modified by setting it to true. Once the environment variables have been added, proceed to save them by clicking 'Apply' and confirming the changes. A confirmation dialog will appear to finalize the operation. Restart the Web App. This second startup may take longer than usual, typically around 5 to 7 minutes, as the environment initializes with the new configuration. Now, as we can see, the application has loaded successfully, and we can start using our own n8n server hosted on Azure. As you can observe, it references the host configured in the App Service. I hope you found this guide helpful and that it serves as a useful resource for deploying n8n on Azure App Service. If you have any questions or need further clarification, feel free to reach out—I'd be happy to help.The Developer’s Guide to Microsoft Azure eBook - August update is now available
Today, we’re pleased to introduce the new and updated Developer’s Guide to Microsoft Azure eBook. Featuring extensive updates since the last update, the new eBook is designed to help you get up to speed with Azure in the shortest time possible and includes practical real-world scenarios. This book includes all the updates from Microsoft Build, along with new services and features announced since then. In addition to these important services, we wanted to focus on practical examples that you’ll use in the real world and included a table and reference architecture that show you “What to use When” for databases, containers, serverless scenarios and more. We also put a key focus on security to help you stop potential threats to your business before they happen. You’ll also see brand new sections on IoT, DevOps and AI/ML that you can take advantage of today. Read about it in the Azure blog.Installation of Azure DevOps Server 2019 RC1 for your Teamwork
What is Azure DevOps Server? Collaborative software development tools for the entire team Previously known as Team Foundation Server (TFS), Azure DevOps Server is a set of collaborative software development tools, hosted on-premises. Azure DevOps Server integrates with your existing IDE or editor, enabling your cross-functional team to work effectively on projects of all sizes. In the following Step-by-Step Guide we will install Microsoft Azure DevOps Server 2019 RC1 Read here more about the simple installation of Azure DevOps Server 2019 RC1Design patterns for microservices
The AzureCAT patterns & practices team has published nine new design patterns on the Azure Architecture Center. These nine patterns are particularly useful when designing and implementing microservices. The increased interest in microservices within the industry was the motivation for documenting these patterns. For each pattern, we describe the problem, the solution, when to use the pattern, and implementation considerations. Read about it on the Azure blog.
