Anthropic Joins Azure: The $30 Billion Partnership Announced at Microsoft Ignite 2025

Microsoft Ignite 2025 delivered one of the most significant AI partnership announcements of the year: Anthropic, the maker of Claude, is now officially part of the Azure ecosystem. This three-way deal between Microsoft, NVIDIA, and Anthropic reshapes the enterprise AI landscape. The Deal The numbers are staggering: Anthropic commits $30 billion to Azure compute capacity Microsoft invests up to $5 billion in Anthropic NVIDIA invests up to $10 billion in Anthropic Anthropic contracts for up to one gigawatt of additional compute power This makes Azure the only cloud provider hosting both OpenAI and Anthropic frontier models—a massive strategic advantage for enterprise customers who want model choice without leaving Microsoft’s ecosystem. ...

November 29, 2025 Â· 2 min

Building an LDAP Proxy for Legacy Applications During Active Directory Migration

During a staged Active Directory migration from Domain A to Domain B, we hit a common but frustrating problem: legacy applications that only support a single LDAP endpoint couldn’t authenticate users split across two domains. This post covers our journey from an overly complex OpenLDAP virtual directory attempt to a simple, effective Python-based solution. The Problem When migrating users between AD domains in stages, you end up with users in both domains simultaneously. Modern applications handle this gracefully with multiple LDAP endpoints or federated identity. Legacy applications? Not so much. ...

November 15, 2025 Â· 3 min

Enabling Multi-Forest Group Membership Coexistence in Entra ID during a Staged Active Directory Migration

During a multi-forest staged migration, where Domain A (source) and Domain B (target) were both synchronizing into a single Entra ID tenant via Entra Connect, we encountered a membership synchronization issue with mail-enabled distribution groups. Although users were successfully matched across forests using ms-ds-consistencyguid, mail-enabled group memberships did not merge. Instead, only one forest’s membership list was applied in Entra ID—regardless of where users actually existed or were migrated. This post explains why that happens, and the precise fix that resolved the issue. ...

November 1, 2025 Â· 4 min