IT staff monitor a secure cloud migration from server racks to a cloud system in a Tokyo operations center.
KDDI iret has signed a Microsoft Cloud Solution Provider (CSP) agreement and is starting a Microsoft services business in Japan. Azure billing, migration and operations services begin on 1 December 2026. This is a partner-channel story, not a new cloud platform. For IT teams in Japan weighing outside help with Azure, Microsoft 365 or the 2016 server migrations, the practical question is what is actually on offer and when.

IT staff monitor a secure cloud migration from server racks to a cloud system in a Tokyo operations center. What was announced, and when​

The dates are easy to blur, so here they are in order:

  • 9 November 2026: the CSP agreement takes effect, per KDDI iret's own announcement.
  • 18 November 2026: the company announces the Microsoft business publicly.
  • 1 December 2026: the first batch of Azure services begins.

Telecompaper's short report describes the deal as covering the design, construction, migration, monitoring and maintenance of Azure environments. The company's own press release gives the detail, summarized below.

The three launch services (1 December)​

  • Azure billing agency. KDDI iret consolidates Azure usage charges into a form that is easier to manage. The stated aim is to cut the accounting workload.
  • Deployment and migration support. This covers requirements definition, design, build and migration from existing environments.
  • Monitoring and managed operations. This is 24/7/365 monitoring and incident response, plus ongoing improvement.

KDDI iret also plans regular free consultation sessions on Azure adoption. They will be held online and in person in Tokyo.

The announcement does not give pricing, customer eligibility, service-level terms, incident response times or the terms of the billing arrangement. Round-the-clock monitoring is a stated feature, not a guaranteed response time. Read it as a description of scope, not a performance commitment.

What comes later (not part of 1 December)​

The company says it will expand "sequentially" into three areas. These are intentions, not launched services.

  • AI and data: Copilot, Microsoft Fabric, Microsoft Foundry and Azure Databricks. The company describes building data foundations and developing AI agents. Example data sources include internal email, meeting records and CRM/ERP systems. It also mentions model selection with cost in mind, agent evaluation and operations, and tidying data-access permissions.
  • Hybrid management and security:
  • Azure Arc for unified management of on-premises and multicloud environments.
  • Entra ID for zero-trust access control.
  • Intune for device management.
  • Purview for information-leak countermeasures.
  • Defender XDR and Microsoft Sentinel for threat monitoring and security operations, coordinated with other KDDI Group companies.
  • Windows Server and SQL Server migration: moving from Windows Server 2016 and SQL Server 2016 to Azure virtual machines and Azure SQL Managed Instance, among other targets.

KDDI iret also plans to pair Azure proposals with its existing cloudpack cloud-support service and gaipack AI solutions. It says it will recruit and train Microsoft-focused engineers.

Why the Windows Server and SQL Server 2016 angle matters​

This is the part with a hard clock on it. Independent lifecycle trackers say Windows Server 2016 reaches end of life on January 12, 2027, when extended support ends. They also report that extended support for SQL Server 2016 ended on 14 July 2026. Because the two products have different dates, each product has its own date, but they often sit on the same machines.

Some practical points from those sources:

  • Without Extended Security Updates (ESU), there are no security updates or support cases after that date. For Windows Server 2016, ESUs are available for Standard and Datacenter editions for up to three years, through 8 January 2030. (The 17 July 2029 date and the Enterprise and Standard editions belong to SQL Server 2016's separate ESU program.)
  • One analysis warns that SQL Server 2025 requires Windows Server 2019 or later, so it won't install on Windows Server 2016. That is one reason the OS and database decisions tend to travel together.
  • Azure SQL Managed Instance, which KDDI iret names, is one of the options in that path. Another analysis lists migrating to Azure SQL, upgrading on a newer Windows Server, or buying ESUs as a short bridge.

KDDI iret's announcement ties its migration offering to this demand and to reviews of VMware environments. It gives no migration deadline, customer numbers or program price. The lifecycle dates above come from third-party trackers and should be checked against Microsoft's lifecycle pages before you plan around them.

Company background and context​

  • KDDI iret says it was established in October 2003.
  • It says it has offered cloudpack since 2010 and has supported cloud adoption for more than 2,500 companies.
  • It says it was an early Japanese AWS Premier-tier partner, and it is a Google Cloud Premier Partner.
  • It was renamed KDDI iret in April 2026 and describes itself as a core AI-integration company in the KDDI Group.

The 2,500 figure covers its historical cloud work overall. It is not a count of Microsoft customers. Microsoft is a new line of business here.

The security argument​

The announcement cites Japan's National Police Agency as reporting 123 ransomware cases in the first half of 2026, a half-year record. It also mentions account takeovers at cloud services. This is KDDI iret's own framing, drawn from a September 2026 NPA report, and I have not independently verified it. It is the company's rationale for pushing identity, device and data-protection services alongside AI.

Comments from Microsoft Japan and KDDI iret​

Tatsuya Mino, Microsoft Japan's channel-partner executive, welcomed KDDI iret's CSP status. He said data foundations, security and cloud environments need to be addressed together as enterprise AI moves from individual productivity to organization-wide change. KDDI iret president Shugo Takagi said adding Microsoft lets the company offer genuine multicloud proposals and support customers beyond trial use of Microsoft 365 and Copilot. Both comments are endorsements of the partnership. Neither is an assessment of how the service performs.

What to make of it​

Why it matters: a CSP is a reseller and managed-services channel for Microsoft cloud. Customers who buy Azure through a partner like this typically get billing and support from the partner. That is how the announced billing agency service works. A company already using KDDI iret for AWS or Google Cloud can now get Azure from the same provider.

What to ask before signing:

  • What are the prices and billing terms for the billing agency service?
  • What response times and service levels apply to the 24/7 monitoring?
  • Which of the AI, security and Windows Server/SQL Server services are actually available at launch?
  • Who holds the Azure tenant and admin rights, and what happens if you leave?

Caveats: the source is mainly the company's own press release. There is no evidence yet of customer uptake or delivery quality. The services start on 1 December, so any judgment on performance has to wait.

For Windows and SQL Server shops in Japan, the clearest takeaway is the 2016 migration support. With Windows Server 2016 support ending on 12 January 2027, the time left to plan is short.


Correction (November 19, 2026): An earlier version of this article said Windows Server 2016 Extended Security Updates were available for Enterprise and Standard editions until 17 July 2029. That date and those edition names belong to SQL Server 2016's ESU program. Windows Server 2016 ESUs cover Standard and Datacenter editions for up to three years, through 8 January 2030.

 

References

  1. KDDI iret launches Microsoft cloud services business in Japan - Telecompaper Telecompaper 2026-11-19T05:21:00+00:00
  2. KDDIアイレット、Microsoft Cloud Solution Provider として Microsoft 事業を開始 | AI とクラウド活用のシステム・アプリ開発なら KDDIアイレット株式会社(iret) iret.co.jp
  3. SQL Server 2016 End of Support: Dates, ESU And Next Steps blog.invgate.com