
The Azure Developer CLI (azd) May and June 2026 combined release covers nine versions (1.24.3 through 1.26.0). Key additions include a new azd tool command group for discovering and managing development tools, azd exec for cross-platform script execution with full azd environment context including Key Vault secrets, Go language support for Azure Functions on Flex Consumption, self-contained extension bundles for registry-free sharing, and per-tenant subscription filters. Safety improvements include an interactive Ctrl+C cancel prompt during provisioning and safer multi-layer provisioning with explicit dependsOn in azure.yaml. Numerous concurrency bugs were fixed, including cross-service image contamination in parallel Container Apps deploys with ACR remote builds, concurrent map write crashes, and parallel dotnet publish race conditions. Authentication fixes address OIDC federated credential mismatches, Cloud Shell credential detection, and stale token caching. Breaking changes affect CI pipelines that parse azd up stage banners.
Nguồn: https://devblogs.microsoft.com/azure-sdk/azure-developer-cli-azd-may-june-2026. 8sync News chỉ tóm tắt và dẫn link; bản quyền nội dung thuộc tác giả và nguồn gốc.
A walkthrough for setting up an apex domain redirect to the www subdomain in Azure Static Web Apps. Covers DNS configuration using CNAME for www and A record for the apex domain, TXT-based domain validation, and using the default domain setting in Azure Portal to trigger the redirect from apex to www automatically.
A practical guide to setting up keyless access to Azure Cosmos DB using managed identities and data plane RBAC. Covers the three key questions for access control: who (managed identity), what (built-in data roles), and where (scope). Explains the critical distinction between control plane and data plane RBAC, walks through assigning the built-in Data Contributor role via Azure CLI, and shows how to use DefaultAzureCredential in the .NET SDK to authenticate without connection strings or secrets.
The European Commission has issued preliminary findings that AWS and Azure should be designated as gatekeepers under the Digital Markets Act, despite neither service meeting the regulation's standard quantitative thresholds. Brussels is invoking the DMA's qualitative route, arguing both platforms serve as critical gateways for EU businesses. If designated, the two cloud giants would face obligations including no self-preferencing, mandated interoperability, and data portability rules aimed at reducing vendor lock-in. The move is partly motivated by cloud infrastructure's growing role as the foundation for AI adoption across Europe. Both Amazon and Microsoft have objected, and a defence phase is now underway before any final decision.
Microsoft has announced the general availability of the Azure Copilot Observability Agent, built on Azure Monitor. The tool correlates logs, metrics, traces, topology, and operational context across environments to help operators move faster from incident detection to root cause resolution. It addresses growing cloud complexity — with 84% of organizations reporting increased complexity and 69% saying it outpaces their operating model — by using AI agents to reason across signals in real time. Customer examples cite reclaiming 250 engineering hours monthly and significantly faster incident resolution. The post frames observability as foundational to a broader shift toward agentic cloud operations, where AI agents continuously interpret signals, take action, and improve system resilience over time, with governance and human oversight remaining essential.

A deep dive into Azure Bicep's conditional (if) and iterative (for) deployment features, covering practical patterns and common pitfalls. Key topics include: guarding references to conditional resources using ternary expressions, the non-cascading nature of conditions on child resources, safe use of runtime functions like listKeys(), resource naming stability in loops, the difference between resource/module loops and variable/output loops, index fragility in filtered loops, and using @batchSize() to control deployment parallelism. Includes a practical checklist and a complete example combining conditionals, filtered loops, batching, and structured outputs.
Part eleven of an event sourcing series explores how to handle consistency boundaries without relying on DDD aggregates or Dynamic Consistency Boundaries (DCBs). The author argues that the best approach depends on the actual problems at hand. Two alternatives are discussed: replacing concurrent designs with non-concurrent ones (e.g., a draft-registration phase processed by a single-threaded algorithm), and using Azure Service Bus sessions to serialize workday validation, eliminating race conditions within a consistency boundary. The post emphasizes solving real problems holistically rather than applying patterns preemptively, and shows how task-based UIs and small data models reduce the likelihood of concurrency conflicts in the first place.

As AI-assisted engineering matures, platform teams need the same controls that make cloud platforms reliable: cost visibility, ownership, sensible defaults, observability, governance, and evaluation loops. Token usage should be treated like CPU or memory — a consumption signal requiring context, not a value proxy. Azure API Management's GenAI gateway capabilities (token rate limits, quota policies, telemetry) provide a shared control point for model consumption. GitHub Copilot usage metrics and team-level reporting help attribute spend. Workload-owned AI resources should be deployed via approved Terraform modules with networking, diagnostics, and tagging baked in. MCP servers and agent skills need explicit ownership and permission models. Governance should work through paved roads — repeatable workflows with evaluation loops — rather than policy documents that teams route around.
Azure RBAC uses a principal + role + scope model to control access across Azure resources. While it provides a solid foundation for access control, it does not automatically enforce least privilege — broad roles like Contributor and Owner get assigned at high scopes for convenience and are rarely revisited. Service principals and managed identities accumulate standing permissions that outlive their projects and rarely appear in access reviews. The post covers RBAC building blocks, common failure patterns (inherited access, non-human identity sprawl, overly broad roles), and best practices including narrowing scope, capping subscription Owners, using just-in-time access via Microsoft Entra PIM, and auditing dormant identities. It concludes by noting that native Azure controls reflect configured state, not actual usage, and promotes a usage-based approach to continuously enforce least privilege.