In August 2025, Microsoft rolled out major updates to how GitHub is licensed and integrated across its ecosystem, and it marks a significant moment for DevOps, security, and AI-powered development. 

GitHub Advanced Security (GHAS) is now built directly into Azure DevOps, and GitHub licenses are being bundled into Microsoft Partner Benefits. Together, these changes show Microsoft’s push toward: 

  • unifying its developer tools
  • strengthening secure coding practices
  • accelerating adoption of GitHub Copilot. 

While the streamlined licensing model and built-in security tooling are a positive for many customers, there are still questions around vendor lock-in and onboarding complexity.

In this article, we'll break down the updates, explore their impact, and outline what IT leaders should do next.

Recent changes - What Microsoft introduced

There are two major updates Microsoft has made that change how teams access GitHub and its security features:

1. GHAS is now native inside Azure DevOps (Sprint 260)

Development teams can now use GitHub Advanced Security features, including secret scanning, dependency scanning, and code scanning, directly from the Azure DevOps environment. What does this mean? It means no switching platforms and no extra tools. Security checks will sit naturally inside the DevOps workflow.

2. GitHub licenses are bundled with Microsoft Partner Benefits (from Jan 22, 2025)

Partners now receive GitHub Enterprise features as part of their benefits package, combined with tools like Microsoft Defender and GitHub Copilot. The result is a more cost-effective, all-in-one licensing model that’s easier to manage and easier to justify.

Why is Microsoft making these moves?

These updates support Microsoft’s long-term strategy: unifying its developer ecosystem under one secure, cloud-native platform. By embedding GHAS into Azure DevOps, Microsoft is:

  • reducing tool fragmentation
  • streamlining DevSecOps workflows
  • nudging customers toward its integrated development stack

Bundling GitHub licenses into partner benefits is another step toward simplifying procurement and onboarding. It encourages organisations already invested in the Microsoft ecosystem to consolidate developer tools, and use GitHub as the default hub for AI-assisted development with Copilot.

This is also aligned with Microsoft's bigger vision of AI-powered software development, where GitHub Copilot becomes central to how organisations write, review, and secure code.

What does this mean for customers? 

At Keystone Negotiation, we see that these changes bring a mix of advantages and new considerations for teams.

The positives:

  • Simplified licensing: fewer SKUs, fewer renewals, easier procurement
  • Stronger security: GHAS in Azure DevOps means vulnerabilities and secrets are caught earlier
  • Cost efficiencies: bundled pricing can reduce overlapping tool spend
  • Better alignment for teams already using Microsoft cloud services

Potential challenges:

  • Greater vendor lock-in: deep integration makes it harder to use independent/non-Microsoft tools
  • Onboarding learning curve: teams unfamiliar with GitHub or Azure DevOps may need time to adapt
  • Workflow transitions could temporarily slow productivity during early adoption

We believe that for many organisations, the benefits will outweigh the challenges, but only if the transition is managed effectively.

Best use cases for the updated licensing model

At Keystone Negotiation, we believe the new GitHub licensing structure is particularly helpful for:

Hybrid cloud teams

Anyone balancing Azure with other cloud environments will benefit from GitHub’s flexibility and Microsoft’s integrated security tooling.

Security-focused development teams

Teams embracing DevSecOps and early-stage security scanning will get real value from native GHAS in Azure DevOps.

Organisations adopting GitHub Copilot

The bundled model makes it easier and more affordable to adopt AI-driven coding tools across entire teams.

Enterprises wanting an end-to-end Microsoft development pipeline

From CI/CD to code scanning to identity management, the licensing evolution creates a more unified development experience.

Looking into the future Outlook - where Microsoft is headed

We expect GitHub to become the default DevOps platform for Microsoft cloud customers. As Microsoft continues integrating GitHub with tools like Defender, Intune, and Copilot Studio, GitHub will sit at the center of:

  • secure coding
  • automated workflows
  • AI-assisted development
  • cloud-native DevOps pipelines

We also expect licensing to continue shifting toward bundled, value-driven packages, making it easier for enterprises to onboard and maximise ROI without managing dozens of separate SKUs.

Over the next few years, GitHub won’t just be a code repository; it will be a fully integrated pillar of Microsoft’s broader enterprise cloud strategy.

Recommendations for IT leaders and licensing managers

1. Review how GHAS fits into your DevSecOps pipeline

Teams already using Azure DevOps should evaluate GHAS and consider moving security checks into the native environment.

2. Reassess your Partner Benefits entitlements

Make sure GitHub licenses are included, activated, and aligned with your existing Microsoft agreements.

3. Evaluate workflow impacts before fully committing

Consider how onboarding, training, and integration with existing tools may affect productivity.

4. Build GitHub (and Copilot) into your broader cloud and AI strategy

Aligning GitHub usage with cloud, identity, and security initiatives will help maximize platform value.

5. Plan for potential vendor lock-in

Understand where dependencies are forming and whether fallback options or dual-tool strategies are needed.

These steps will help organisations transition smoothly, reduce licensing waste, and take advantage of Microsoft’s increasingly unified developer ecosystem. 

Need guidance navigating these Microsoft changes?

At Keystone Negotiation, we help organisations make sense of evolving Microsoft licensing models, including GitHub, Azure DevOps, Copilot and broader cloud agreements. If you want to understand how these updates affect your renewals, your costs, or your DevOps roadmap, our team can walk you through the details and help you negotiate the right outcome for your organisation. Get in touch today!

References

  • GitHub Advanced Security for Azure DevOps – Sprint 260
    Microsoft Partner Benefits Update – January 2025