Period: today · Items: 5 · Source: Azure official updates RSS
Today’s updates are quite practical and operations-focused. On the AI side, GA/Preview playground experiences are now available for document-based PII detection, making it easy to try them out right away. On the infrastructure side, Instant Access for VM recovery scenarios, which helps reduce perceived RTO, and support for GCS→Azure Blob migration stand out. Added to that is the GA release of the PowerShell module for PostgreSQL Flexible Server, making today a great day to study experimental AI features + operations automation + recovery/migration all at once.
· Document PII detection — You can quickly validate document-level personal information detection with sample inputs and get a feel for the difference between text PII and document PII.
· Playground-driven evaluation — With a portal playground, you can quickly assess model/feature fit even before making API calls.
· Application-consistent restore point — Understanding the concept of a recovery point that considers application consistency, not just a simple snapshot, makes DR design easier.
· Lower RTO with Instant Access — You can see how starting disk restore without waiting for background replication affects recovery time objectives (RTO).
· Cross-cloud data migration — The flow of moving data from GCS to Azure Blob is a good way to study multi-cloud operations, data gravity, and criteria for selecting migration tools.
· A new playground for document-based PII detection in Azure AI Language is now generally available.
· It includes prepared sample inputs and outputs so you can start evaluating the feature more quickly.
· You can experience the full flow of detecting personal information in documents and reviewing redaction results directly in the portal.
· It is useful for feature-fit reviews or demos before API integration.
What it is: This feature lets you test document-based personal information detection (Document PII) in Azure AI Language directly in the NextGen Playground. The key point is that you can quickly review detection and masking results based on document input, not just simple text snippets.
Why it matters: In real-world scenarios, teams often want to know, “Does this actually work well for this type of document?” before developing against the API. A playground like this helps you quickly build intuition about model performance and reduce trial and error when designing PII protection workflows.
Try it: Open the Document PII playground in the Azure AI Language portal, review the sample document results, and note which types of entities are detected and masked.
Source: https://azure.microsoft.com/updates?id=564382
· An initial playground experience for document-based PII detection is available in the Microsoft Foundry NextGen portal.
· You can load prepared sample documents and run the document-based PII feature.
· You can review redacted output in the results, making it easy to visually understand how the feature works.
· As this is a Preview with the nature of an “initial playground experience,” it is best suited for learning and evaluation purposes.
What it is: This is a Preview sample playground built to let you experience document-based PII detection from Azure AI Language inside the Microsoft Foundry NextGen portal. The flow of uploading a sample document and immediately viewing results serves as a learning resource in itself.
Why it matters: Even for the same PII detection capability, “reading the API spec” and “putting in a document and seeing the results” provide very different learning efficiency. Especially for engineers evaluating AI features for the first time, a playground-centered exploration approach is highly helpful for clarifying requirements.
Try it: In the relevant sample in the Microsoft Foundry NextGen portal, review the results based on the prepared sample document and compare how closely the redaction results match your actual internal document scenarios.
Source: https://azure.microsoft.com/updates?id=563331
· A newly named PowerShell module for managing Azure Database for PostgreSQL Flexible Server has reached GA.
· It is described as providing a more streamlined management experience based on existing Az.PostgreSql-related functionality.
· It is a good starting point as the standard module for automating PostgreSQL Flexible Server operations.
· It is useful for PowerShell-based operations or platform teams building a consistent management framework.
What it is: This update announces the general availability of Az.PostgreSQLFlexibleServer, a dedicated PowerShell module for managing Azure Database for PostgreSQL Flexible Server. It appears to carry forward the existing command set while offering a more organized naming convention and experience.
Why it matters: If you only learn the GUI when studying Azure, it is easy to hit a wall when you move into operations automation. Practicing how to view database services from an IaC/scripting perspective helps you connect provisioning, configuration, validation, and operational standardization more naturally.
Try it: Review the Az.PostgreSQLFlexibleServer module documentation in your local PowerShell environment, and start by running commands to inspect and verify Flexible Server configuration in a test subscription.
Source: https://azure.microsoft.com/updates?id=566209
· Azure Storage Mover now supports cloud-to-cloud migration from Google Cloud Storage to Azure Blob Storage.
· The update introduces a method for transferring data from GCS using an S3-compatible interface.
· This adds another option for consolidating data into Azure in multi-cloud environments.
· It is useful for learning Blob-centric data lake, backup, and archive relocation scenarios.
What it is: This Preview feature allows Azure Storage Mover to take GCS as a source and move data into Azure Blob Storage. In addition to on-premises file migrations, it now supports a more direct path for bringing data into Azure from another cloud storage platform.
Why it matters: When studying Azure, many people think only “within Azure,” but in real enterprise environments, most projects involve moving from another cloud or an existing environment. This feature helps you see migration tools not just as copy tools, but as part of a cloud transition strategy.
Try it: Sketch a simple migration flow assuming a GCS bucket and an Azure Blob container, and identify at which stages Storage Mover handles authentication, copy, and validation.
Source: https://azure.microsoft.com/updates?id=566948
· Instant Access has been introduced for Azure VM Restore Points, allowing disk restore to begin immediately after a restore point is created.
· The key benefit is that you no longer need to wait for background data replication to finish.
· As a result, it is meaningful for scenarios targeting faster recovery, or lower RTO.
· Because it is based on application-consistent restore points, it is also a good opportunity to study recovery flows that account for consistency.
What it is: This is a Preview feature that enables more immediate disk restore based on application-consistent restore points, rather than waiting for replication to complete after creating a VM Restore Point and only then restoring.
Why it matters: When studying backup and recovery, what matters more than the storage mechanism is “how quickly can the service be restored?” This feature helps you understand how Azure is shaping the user experience to reduce RTO, beyond just snapshot/restore concepts.
Try it: First summarize the concepts of VM Restore Point and application-consistent restore point, then compare the steps in the traditional recovery flow versus the Instant Access flow in a table.
Source: https://azure.microsoft.com/updates?id=565758
There are no separate retirement items in today’s list.