• Microsoft Azure showcased modernization of cloud infrastructure at Microsoft Ignite 2025, focusing on reliability, security, and AI-era performance.
• The strategy includes strengthening Azure’s global foundation, modernizing workloads with advanced systems (Azure Cobalt, Azure Boost, AKS Automatic, HorizonDB), and transforming team workflows through AI agents like Azure Copilot and GitHub Copilot.
• Azure Copilot introduces an agentic cloud operations model with specialized agents for migration, deployment, optimization, observability, resiliency, and troubleshooting to automate tasks and enhance innovation.
• Azure’s AI infrastructure supports global scale with over 70 regions and datacenters, featuring Fairwater AI datacenters with liquid cooling, a dedicated AI WAN, and NVIDIA GB300 GPUs to deliver unmatched capacity and speed.
• Innovations like Azure Boost offload virtualization tasks onto specialized hardware, improving disk throughput and network performance; AKS Automatic simplifies Kubernetes management for fast, reliable app deployment.
• Azure HorizonDB for PostgreSQL offers scalable, AI-integrated databases and new partnerships (e.g., SAP Business Data Cloud Connect) facilitate data sharing across platforms.
• Azure emphasizes operational excellence with zone-redundant networking, automated fault detection, and resilience co-engineered with customers via Azure Resiliency.
• Security improvements include Azure Bastion Secure by Default for hardened VM access, Network Security Perimeter for centralized firewall control, and AI-powered defenses like Web Application Firewall with Captcha.
• Modernization supports a mix of legacy and cloud-native systems with AI tools enabling faster migration and modernization for .NET, Java, SQL Server, Oracle, and PostgreSQL workloads.
• Azure enables faster, more efficient modernization and management across infrastructure, improving governance, compliance, and cost-effectiveness.
• The cloud future is agentic, intelligent, and human-centered, with continued innovation in Azure infrastructure, AI agents, and open-source contributions driving business growth.

Learn how to build a scalable serverless web app using Azure. This guide walks you through Azure Functions, App Service, and best practices for cloud-native development.

Unlock next-gen business growth by building AI-powered enterprise applications using Microsoft Azure. Discover how Azure AI services, machine learning, and scalable cloud infrastructure empower businesses to streamline operations, drive automation, and make data-driven decisions with confidence.

Direct line secrect 和 Drect line toke 是不一样的。

Signalr API Support Server - to - client 的 Broadcast 类型的。

AZ 900

This is my first every hypothesis note.

So far I have the done the first test, and found it relevant. Well worth the money so far.

Since it is a Platform as a Service, it isolates the configuration required to perform scaling from the users, allowing them to focus on their data manipulation.

so they said replicated, not fragmented.

Model deployment in Azure ML

That is, to request token if the app is not running in the Azure cloud with a managed identity:

• Acquire a token from Azure AD for authorizing requests from a client application

• Request an access token in Azure Active Directory B2C (and the other chapters in the Authorization protocols section)

Here's why it's important to revoke access (rom Upload a VHD to Azure or copy a managed disk to another region - Azure PowerShell):

After the upload is complete, and you no longer need to write any more data to the disk, revoke the SAS. Revoking the SAS will change the state of the managed disk and allow you to attach the disk to a VM.

Couldn't find where the exhaustive list of API versions are listed, but found this on the Azure Instance Metadata Service (aka IMDS) page:

2017-04-02, 2017-08-01, 2017-12-01, 2018-02-01, 2018-04-02, 2018-10-01, 2019-02-01, 2019-03-11, 2019-04-30, 2019-06-01, 2019-06-04, 2019-08-01, 2019-08-15

Also:

The version 2019-11-01 is currently getting deployed and may not be available in all regions.

Azure ACI doesn't accept privileged containers. (--cap-add=NET_ADMIN)