Azure Beginner to Hero

Retirement of DCsv2-series Azure Virtual Machines The DCsv2-series Azure Virtual Machines are scheduled for retirement on June 30, 2026 [1][2][3]. This means that after this date, these virtual machines will no longer be available for use. Here is a summary of key points related to this retirement: Key Points Retirement Date : June 30, 2026[1][2][3]. Impact : This retirement affects anyone using DCsv2-series virtual machines, including those on Azure Kubernetes Service and Azure Virtual Machine Scale Sets[1]. Migration Recommendation : Users are advised to migrate their workloads to DCdsv3-series virtual machines or consider alternatives like DCasv5/DCadsv5/ECasv5/ECadsv5 VMs, DCasv6/ECasv6 series , or Azure Confidential Container Instances (C-ACI) [1]. New Sign-Ups : Starting from July 1, 2025 , no new subscriptions will be allowed for DCsv2-series virtual machines due to capacity restrictions[1]. Ongoing Support Microsoft will continue to provide support, including SLA as...

Azure Site Recovery (ASR) has officially launched general availability support for Azure Trusted Launch virtual machines (VMs) running Linux operating systems. This means that Azure customers can now use ASR to provide disaster recovery and replication capabilities for Linux VMs secured with Trusted Launch, a feature that enhances VM security through mechanisms like Secure Boot and measured boot. Key details include: Supported Linux distributions: ASR supports Trusted Launch VMs running major Linux distributions such as Ubuntu (18.04, 20.04, 22.04, 24.04), Red Hat Enterprise Linux (various 8.x and 9.x versions), SUSE (15 SP3 to SP6 with specific kernel versions), Alma Linux (8.10, 9.4, 9.5), and Debian 12[1]. Support status: Previously, ASR support for Trusted Launch was generally available for Windows VMs, while Linux support was only in private preview. As of now, Linux Trusted Launch VM support has transitioned out of preview to general availability, providing full disaster r...

Overview of Azure Command Launcher for Java The Azure Command Launcher for Java, referred to as jaz , is a new utility designed to simplify running Java applications on Azure. It aims to optimize Java Virtual Machine (JVM) configurations specifically for cloud environments, ensuring better resource utilization and efficiency from the outset[1][2]. Key Features and Benefits Optimized JVM Configurations : jaz provides default configurations tailored for Azure deployments, addressing the common issue of suboptimal resource usage when relying on default JVM settings[2]. Advanced JVM Features : It leverages features like AppCDS and plans to support Project Leyden in the future, enhancing performance and startup times for Java applications[2]. Support for Containers and VMs : Designed to work seamlessly with containers and virtual machines, making it suitable for modern cloud-native applications[2]. Current Status As of June 2025, the Azure Command Launcher for Java is in a private...

Azure Virtual Network Manager in Azure China Azure Virtual Network Manager has reached general availability in Azure China, marking a significant milestone in enhancing network connectivity and management capabilities for customers in the region. This update was announced on June 10, 2025, and it includes features related to connectivity, security administration, and routing configuration[1]. Key Features and Benefits Connectivity Management : The Azure Virtual Network Manager allows for centralized management of network architecture, simplifying the organization and administration of virtual networks. Security Administration : Enhanced security features help protect network resources by providing better control over network security policies. Routing Configuration : Customers can configure routing settings more efficiently, ensuring optimal network performance and reliability. Availability and Impact This general availability in Azure China aligns with Microsoft's broade...

Overview of Persistent Graph Semantics in Azure Data Explorer Azure Data Explorer has introduced a new feature in public preview: Persistent Graph Semantics, also known as Persistent Graphs. This feature allows users to work with durable graph data structures that persist beyond individual queries, enhancing performance and efficiency in complex relationship-based analyses[1][3]. Key Features of Persistent Graphs Graph Models : These are stored representations of labeled property graphs (LPGs) that consist of nodes (vertices) and edges (relationships), both of which can have properties. Unlike transient graphs, graph models do not require rebuilding for each query, significantly improving performance[3]. Metadata Persistence : Graph specifications are stored in database metadata, ensuring durability and reusability[3]. Materialized Snapshots : These eliminate the need to rebuild graphs for each query, dramatically improving query performance[3]. Schema Definition : Graph models...

ใน EP นี้ของ Azure Talk – 3 Minutes คุณจะได้เรียนรู้ว่า การย้ายระบบองค์กรขึ้น Azure ให้สำเร็จ ไม่ใช่แค่ "โยน VM ขึ้นคลาวด์" เท่านั้น! Microsoft Cloud Adoption Framework (CAF) แนะนำแนวทาง “Adopt” ด้วย 3 เสาหลัก: Migrate ระบบแบบเดิม (Lift-and-Shift) Modernize ปรับโครงสร้างให้คลาวด์เนทีฟ Innovate สร้างแอป/บริการใหม่โดยใช้ AI, Serverless หรือ Analytics คุณจะได้เข้าใจ: ขั้นตอน 4 Step ใน CAF Migrate การเลือกใช้ทั้ง 3 แนวทางควบคู่ ตัวอย่างจริงที่ช่วยให้ระบบเสถียร ปลอดภัย และพัฒนาต่อได้เร็วขึ้น เหมาะกับทั้ง IT Admin, Architect, และคนวางแผนระบบระดับองค์กร

Azure Database for PostgreSQL - Azure Data Factory Managed Identity The Azure Database for PostgreSQL now supports managed identity for integration with Azure Data Factory , enhancing secure data integration processes. This integration leverages managed identities to authenticate connections, eliminating the need for hardcoded credentials. Key Features of Managed Identity Integration Authentication Methods : Azure Database for PostgreSQL flexible server supports various authentication methods for Azure Data Factory, including basic authentication, service principal, system-assigned managed identity, and user-assigned managed identity[2]. Managed Identity Benefits : Managed identities are automatically managed by Azure, reducing the complexity of credential management. They allow applications to access resources without explicitly handling credentials[1][4]. Azure Data Factory Capabilities : Azure Data Factory is a fully managed service designed for data integration tasks like E...

PostgreSQL 17 In-Place Upgrade on Azure Database for PostgreSQL Flexible Server Overview Azure Database for PostgreSQL flexible server now supports an in-place major version upgrade to PostgreSQL 17, currently available in public preview. This upgrade allows users to move from PostgreSQL versions 14, 15, or 16 to PostgreSQL 17 without data migration or changes to connection strings, simplifying the process for users and applications[1][3]. Key Features of the Upgrade No Data Migration Required : The upgrade process does not require moving data, which reduces complexity and downtime[4]. No Changes to Connection Strings : Applications can continue to use existing connection strings, ensuring minimal disruption[3]. In-Place Upgrade Capability : This feature is designed to minimize user and application disruption by retaining server settings and name post-upgrade[4]. How to Upgrade Users can upgrade their PostgreSQL versions using either the Azure Portal or the Azure CLI : Azu...

Summary of Azure Update and Private Endpoint Configurations Overview of Azure Update As of June 3, 2025, Microsoft Azure has made a required role assignment for private endpoint approvals generally available in Azure Machine Learning (AzureML) workspaces and/or AI Foundry hubs with managed networks[1]. This update emphasizes the need for explicit role assignments for securing private endpoint connections. Details on Private Endpoint Configurations To configure private endpoints in Azure Machine Learning, users must follow specific steps to ensure secure connections: Role Assignment : The Azure Machine Learning workspace's managed identity must have permissions to approve Private Endpoint connections on target resources. This is typically done by assigning the Azure AI Enterprise Network Connection Approver role or a custom role with similar permissions[3]. Target Resources : The Azure AI Enterprise Network Connection Approver role covers a wide range of Azure resources, in...

Summary of Long-Term Backup Retention for Azure Database for PostgreSQL – Flexible Server Long-term backup retention for Azure Database for PostgreSQL – Flexible Server is now generally available, offering enhanced capabilities for compliance, audit readiness, and data durability. This feature is part of Azure Backup, which provides a robust solution for securing data against various threats. Key Features of Long-Term Backup Retention Retention Period : Backups can be retained for up to 10 years , addressing regulatory and compliance needs that exceed the standard 35-day operational tier backup limit[2][3]. Security and Durability : Backups are encrypted and stored in a separate security domain, protecting against ransomware attacks and accidental deletion. The service also offers immutability and soft delete protection[3]. Policy-Driven Management : Users can define custom backup policies with flexible scheduling and retention rules, allowing for granular control over backup ...

คุณรู้หรือยังว่า Windows Server หรือ SQL Server ที่คุณใช้งานอยู่... อาจหมดอายุจาก Microsoft แล้วแบบไม่รู้ตัว! ใน EP นี้ของ Azure Talk – 3 Minutes เราจะพาคุณเข้าใจ Product Lifecycle ของ Microsoft – Mainstream Support คืออะไร? – Extended Support ต่างยังไง? – ทำไม End of Support ถึงอันตรายต่อองค์กร? – และถ้าระบบคุณหมดอายุแล้ว ควรทำอย่างไร? 📍 ฟังจบใน 3 นาที คุณจะรู้ว่า... ระบบที่คุณดูแล ควรอัปเกรดหรือย้ายขึ้น Azure ด่วนแค่ไหน

🎯 อยากรู้ไหมว่าองค์กรใหญ่ ๆ เขาออกแบบ EA ยังไงกันจริง ๆ? EP7 นี้คุณ B และคุณ Lee จะพาคุณเจาะลึก Case Study จริงจากองค์กรระดับโลก ✅ เห็นภาพการนำ EA ไปใช้จริง ✅ เรียนรู้วิธีลดความซับซ้อนของระบบ ✅ จัดการโครงสร้างองค์กรแบบมืออาชีพ 👩‍💼 ฟังเรื่องจริงจากองค์กรที่ "ทำได้จริง" 📺 รับชมได้ทุกวัน เวลา 20.00 น. ทาง YouTube ช่อง: ไอไลค์ไอที ดอด อินโฟ

🎧 EP8 ปิดซีรีส์ EA Cloud Talk อย่างเต็มระบบ! ในตอนสุดท้ายนี้ เราพาคุณไปรู้จัก 5 เครื่องมือที่ Cloud Architect ทุกคนควรมี เพื่อวาง EA ให้ใช้งานได้จริงในองค์กร ✅ จากแค่แผน → สู่ระบบจริง ✅ ใช้ได้กับ Azure, AWS, GCP ✅ ครอบคลุมทั้ง Infra, DevOps, Business Alignment 🎯 และนี่คือ ตอนสุดท้ายของซีรีส์ EA Cloud Talk ขอบคุณทุกการฟัง แชร์ และแรงสนับสนุนตลอด 8 ตอนที่ผ่านมา 🙏 📺 ดูย้อนหลังทุกตอนได้ที่ช่อง YouTube: ไอไลค์ไอที ดอด อินโฟ และเตรียมพบกับพอดแคสต์รายการใหม่ Podcast IT เร็ว ๆ นี้!

The Azure Synapse Runtime for Apache Spark 3.4 was released as generally available (GA) on November 21, 2023, succeeding Apache Spark 3.3 in Synapse Analytics. It offers performance improvements, new features, and enhanced security. Users were encouraged to upgrade from older runtimes like 3.3 to 3.4, with a recommended migration plan involving assessment of compatibility, codebase analysis, and creation of new Spark pools for testing purposes[1]. Regarding its retirement, Azure announced that the Azure Synapse Runtime for Apache Spark 3.4 will be retired in March 2026. This means support for this runtime will end at that time, and customers should plan to migrate their workloads to newer supported runtimes before this date[3][5]. In summary: Release : Apache Spark 3.4 runtime for Azure Synapse became GA in November 2023. Upgrade advice : Users should test and migrate workloads from versions 2.4, 3.1, 3.2, or 3.3 to 3.4 to benefit from improvements. End of support / Retirement :...

Azure Backup has introduced public preview support for Azure Elastic SAN, providing a fully managed solution for backing up and restoring Elastic SAN volumes. This integration enables users to take instant point-in-time backups of Elastic SAN workloads, enhancing data protection and recovery capabilities for enterprise storage in the cloud[1][2]. Azure Elastic SAN itself is a cloud-native, fully managed storage area network (SAN) service designed to deliver high throughput, low latency, and enterprise-grade block storage, suitable for both migrated on-premises SAN workloads and new cloud applications. Key features include autoscale for capacity, snapshot capabilities, private endpoint support for secure network access, and shared volumes with SCSI Persistent Reservations allowing multiple compute clients to access a volume safely and concurrently[2][3][5]. The integration of Azure Backup with Elastic SAN allows users to: Efficiently back up Elastic SAN volumes with minimal operati...

Here is a summary based on the information from the Azure Migrate update and supporting documentation: Azure Migrate Support for Premium SSD v2 Disks – General Availability Overview Enhanced Support: Azure Migrate now generally offers support for Premium SSD v2 disks as part of migration projects. This enables organizations to leverage high-performance, cost-effective storage options for migrated workloads. Premium SSD v2 Features: These disks are designed for IO-intensive enterprise workloads, providing sub-millisecond disk latencies, high IOPS, and throughput at a lower cost compared to previous generations[2]. Migration Process: Migrating to Premium SSD v2 requires using snapshots—specifically, incremental snapshots for certain disk types (like Standard HDD, Standard SSD, or Premium SSD) when targeting Premium SSD v2 or Ultra Disks. Direct conversion is not supported for all scenarios, so migration via snapshots is recommended[1][5]. Limitations: Premium SSD v2 and Ultra...

Here is a structured summary of the Generally Available: Private Subnet launch announcement and key information from the official Azure Updates page referenced (https://azure.microsoft.com/updates?id=492953): General Availability of Azure Private Subnet Announcement Date: May 2025[1] Feature Status: Launched (now generally available for all Azure customers) Description: The "private subnet" feature for Azure Virtual Network is now production-ready, enabling customers to create subnets with enhanced network isolation and security. Key Benefits: Enhanced Security: Private subnets help restrict outbound internet access, reducing the risk of unauthorized data exfiltration. Explicit Internet Access: VMs in a private subnet do not have default outbound internet access, requiring explicit configuration of NAT gateways or other routes for connectivity[5]. Greater Control: Organizations gain more granular management over their Azure VM network traffic, allowing them t...

Summary of Azure Load Testing Updates Managed Identity Support Azure Load Testing now supports managed identity-based authentication flows , which allows users to securely simulate authentication requests without using passwords or keys. This feature is generally available and enables more secure authentication methods for load testing scenarios[4][5]. Key Features: Security : Managed identities provide a secure way to authenticate without exposing credentials, aligning with Azure's security initiatives[3][5]. Ease of Use : The feature simplifies the setup of load tests by allowing users to select managed identities directly in their test configurations[3]. Flexibility : It supports both system-assigned and user-assigned managed identities, giving users flexibility in managing access permissions[1][3]. Update on Azure Load Testing As of the latest updates, Azure Load Testing has enhanced its capabilities to support advanced authentication flows, ensuring that load tests ...

Certainly! Here’s a concise, expert summary of the recent launch and Microsoft Update for Change Streams for Azure Cosmos DB for MongoDB (vCore) . Overview Feature Launch: Change Streams for Azure Cosmos DB for MongoDB (vCore) is now generally available (GA)[1][3][5]. Purpose: Enables applications to react instantly to data changes in the vCore-based Azure Cosmos DB for MongoDB. Benefits: Supports real-time scenarios such as live dashboards, alert systems, and reactive applications by streaming database changes directly to your app[2][3][5]. Key Features and Details Real-Time Data Streaming: Change streams allow your application to subscribe to database changes, eliminating the need for continuous polling[2]. Cluster Support: Currently supported for single-shard clusters; multi-shard cluster support is in development[2]. Limits: Azure Cosmos DB for MongoDB (vCore) enforces a 400 MB limit on change streams; a support request is required to increase this limit[2]. Mana...