Enterprises and teams are adopting DevOps technologies combined with people and processes to deliver high-quality code, with faster release cycles and continuous delivery of value, to achieve higher levels of satisfaction for their own customers.
However, it can often get difficult to craft CI/CD pipelines by editing multiple YAMLs to stitch your code to cloud automation workflows. Teams end up spending considerable time and effort setting up and switching between different discrete tools during their day-to-day development cycles.
In November, GitHub Actions for Azure became generally available to automate deploying your app code in GitHub to Azure directly from their repositories. Building on this, at Microsoft Build 2020 we announced that GitHub Actions for Azure are now integrated into Visual Studio Code, Azure CLI, and the Azure Portal simplifying the experience of deploying to Azure from your preferred entry points. Download the new Visual Studio Code extension or install the Azure Command-Line Interface (CLI) extension for GitHub Actions.
GitHub Actions for Azure can now deploy any enterprise application
GitHub Actions gives you the flexibility to build an automated software development lifecycle workflow. To help development teams easily create workflows to build, test, package, release, and deploy to Azure, more than 30 GitHub
Welcome to Microsoft Build 2020! This all-new 48-hour digital experience is designed to help you and other developers around the world come together to solve challenges, share knowledge, and stay connected. Here we’ll cover some of our latest innovations in developer tools and cloud platform technologies—to help you code, collaborate, and ship your apps from anywhere, so you can support the changing needs of your business and continue to deliver the quality experiences that your customers expect.
So how do you overcome the challenges of today and remain productive as developers? Thankfully, in today’s digital world there are tools to help you work remotely and be as productive as ever: with Azure as your trusted cloud platform and cloud-powered developer tools with Visual Studio and GitHub.
Developers often spend endless hours configuring dev machines for new projects: cloning source code, installing runtimes, setting up linters and debuggers, configuring extensions—just to do it all again for the next project, the next bug, or the next code review. The challenge is even more prevalent in times of remote work, where you might not have access to your preferred development machine. Visual Studio Codespaces, available in preview, enables you to create a
Azure Container Registry announces dedicated data endpoints, enabling tightly scoped client firewall rules to specific registries, minimizing data exfiltration concerns.
Pulling content from a registry involves two endpoints:
Registry endpoint, often referred to as the login URL, used for authentication and content discovery.
A command like docker pull contoso.azurecr.io/hello-world makes a REST request which authenticates and negotiates the layers which represent the requested artifact. Data endpoints serve blobs representing content layers.
Registry managed storage accounts
Azure Container Registry is a multi-tenant service, where the data endpoint storage accounts are managed by the registry service. There are many benefits for managed storage, such as load balancing, contentious content splitting, multiple copies for higher concurrent content delivery, and multi-region support with geo-replication.
Azure Private Link virtual network support
Azure Container Registry recently announced Private Link support, enabling private endpoints from Azure Virtual Networks to be placed on the managed registry service. In this case, both the registry and data endpoints are accessible from within the virtual network, using private IPs.
Unfortunately, virtual network connectivity isn’t always an option.
Incremental enrichment is a new feature of Azure Cognitive Search that brings a declarative approach to indexing your data. When incremental enrichment is turned on, document enrichment is performed at the least cost, even as your skills continue to evolve. Indexers in Azure Cognitive Search add documents to your search index from a data source. Indexers track updates to the documents in your data sources and update the index with the new or updated documents from the data source.
Incremental enrichment is a new feature that extends change tracking from document changes in the data source to all aspects of the enrichment pipeline. With incremental enrichment, the indexer will drive your documents to eventual consistency with your data source, the current version of your skillset, and the indexer.
Indexers have a few key characteristics:
Data source specific. State aware. Can be configured to drive eventual consistency between your data source and index.
In the past, editing your skillset by adding, deleting, or updating skills left you with a sub-optimal choice. Either rerun all the skills on the entire corpus, essentially a reset on your indexer, or tolerate version drift where documents in your index are enriched with different versions of
Organizations and teams that adopt DevOps methodologies are consistently seeing improvements in their ability to deliver high-quality code, with faster release cycles, and ultimately achieve higher level of satisfaction for their own customers, whether they’re internal or external. Continuous Integration and Continuous Delivery (CI/CD) is one of the pillars of DevOps, consisting in automatically building, testing and deploying applications, but setting up a full CI/CD pipeline can be a complex task.
Today, we’re sharing the launch of the Deploy to Azure extension for Visual Studio Code. This new extension allows developers working in Visual Studio Code to seamlessly create, build, and deploy their apps in a continuous manner to the cloud, without leaving the editor.
Deploy to Azure extension
The Deploy to Azure extension works with both GitHub Actions and Azure Pipelines. It helps developers by auto-generating a CI/CD pipeline definition that takes care of building and deploying your app to the cloud with Azure. You can use Deploy to Azure extension to deploy application code present in your local system, or in Azure Repos or GitHub. We plan to expand the scope to other Git repositories in future.
You can use this extension to set up CI/CD pipeline for
https://azure.microsoft.com/blog/sql-server-runs-best-on-azure-heres-why/SQL Server customers migrating their databases to the cloud have multiple choices for their cloud destination. To thoroughly assess which cloud is best for SQL Server workloads, two key factors to consider are: Innovations that the cloud provider can uniquely READ MORE
As 2020 is upon us, it’s natural to take time and reflect back on the current year’s achievements (and challenges) and begin planning for the next year. One of our New Year’s resolutions was to continue live streaming software development topics to folks all over the world. In our broadcasts in late November and December, the Azure community saw some of our 2020 plans. While sharing, many others typed in the chat from across the world that they’d set a New Year’s resolution to learn Azure and would love any pointers.
When we shared our experiences learning Azure in the “early days,” we talked about the number of great resources (available at no cost) users can take advantage of right now, and carry their learnings into the new year and beyond.
Here are a few tips for our developer community to help them keep their resolutions to learn Azure:
Create a free account: The first thing that you’ll need is to create a free account. You can sign up with a Microsoft or GitHub account and get access to 12 months of popular free services, a 30-day Azure free trial with $200 to spend during that period and over 25
Last month, we started sharing the DevOps journey at Microsoft through the stories of several teams at Microsoft and how they approach DevOps adoption. As the next story in this series, we want to share the transition one team made from a classic operations role to a Site Reliability Engineering (SRE) role: the story of the Xbox Reliability Engineering and Operations (xREO) team.
This transition was not easy and came out of necessity when Microsoft decided to bring Xbox games to gamers wherever they are through cloud game streaming (project xCloud). In order to deliver cutting-edge technology with top-notch customer experience, the team had to redefine the way it worked—improving collaboration with the development team, investing in automation, and get involved in the early stages of the application lifecycle. In this blog, we’ll review some of the key learnings the team collected along the way. To explore the full story of the team, see the journey of the xREO team.
Consistent gameplay requirements and the need to collaborate
A consistent experience is crucial to a successful game streaming session. To ensure gamers experience a game streamed from the cloud, it has to feel like it is running on a nearby
https://azure.microsoft.com/blog/achieve-operational-excellence-in-the-cloud-with-azure-advisor/Many customers have questions when it comes to managing cloud operations. How can I implement real-time cloud governance at scale? What’s the best way to monitor my cloud workloads? How can I get help when I need it? Azure offers READ MORE
https://azure.microsoft.com/blog/faster-and-cheaper-sql-on-azure-continues-to-outshine-aws/Over a million on-premises SQL Server databases have moved to Azure, representing a massive shift in where customers are collecting, storing, and analyzing their data. Modernizing your databases provides the opportunity to transform your data architecture. SQL Server on Azure READ MORE