Currently KMS, B&A, and KV services support GCP and AWS without support for the second largest cloud provider (Azure). Implementations for AWS and GCP predated any publicly-defined process/mechanism and were approved ~7mo ago in April 2024 (#63, #64). Support for Azure has been requested numerous times, via multiple channels as has been discussed in (#31) with a formal request made in this thread ~6mo ago with a quick ack on reviewing but no formal approval or updates.

In parallel the Chrome browser has carried out Origin Trials, and is looking to ship the B&A APIs as we speak (Blink-Dev Intent to Ship Bidding & Auction APIs). Given Chrome efforts to ship the corresponding B&A APIs we are deeply concerned that it will leave no chance for ad tech entities that depend on Azure to evaluate these solutions in Azure or provide meaningful feedback.

Our Azure R&D and security experts have had initial PRs open to provide either direct contributions, or fully functionally example code/implementations to the team (however you wish to use this) for >11mo with no comments, feedback, or other action: PR: privacysandbox/data-plane-shared-libraries#1. For convenience a new PR has been updated with the latest/complete Azure CPIO/dataplane support rebased to the HEAD of the dataplane branch. We are happy to promptly address feedback, make direct contributions (split the PR up as needed), or provide consultation with the specifics of how to adapt the existing code for operation in Azure.

Given this background, @chatterjee-priyanka , @renanfel , can you and the team please help provide feedback on timelines for supporting Azure, how it integrates with any efforts we've heard about relating KMS/coordinator re-architecture (#69), and what concerns or impediments there may be to accepting direct contributions to start unblocking things in this space by contributors already covered by a Google CLA?