Pinned Posts
Forum Widgets
Latest Discussions
TLS 1.0 and 1.1 Support on Azure Web App
I know Azure is winding up support for TLS 1.0 and 1.1 by August 2025. Does anyone can help me to access our existing IoT devices to connect to Azure Web App using this TLS 1.0 and 1.1? Our device were connecting to azure server fine until Mid March 2025. At end of March 2025 we lost access to this IoT devices which uses TLS 1.0, 1.1. Any thoughts or any one have any idea why it stopped before the deadline of August 2025? And what can be done to get back this devices online? #IoTHub #WebApp #Azure #TLS #TLS1.0 #TLS1.1 #SNI
Azure Migrate Appliance
Hi, We are planning to migrate 100 servers to Azure and are looking for guidance on deploying the Azure Migrate appliance. Due to space limitations on-premises, we do not have room to deploy the appliance locally. Is it possible to deploy the Azure Migrate appliance in an Azure virtual machine (VM) within our existing Azure subscription? if so we would like to deploy the VM, install the Azure Migrate appliance, and then use it to assess, discover, and perform dependency analysis for our on-premises virtual and physical servers. Additionally, we are considering using the "Physical Server" option by downloading the installer script from the Azure Migrate appliance. Can you please confirm if this approach is viable, are there any additional steps or considerations we should be aware of by deploying the appliance in Azure on a VM. ThanksMS SQL in Azure VM to SQL PaaS Migration
What are the current best practices for migrating a SQL Server hosted in an Azure VM to Azure SQL Database? I’m looking to approach this in two phases: Assessment followed by Migration. There are several tools available for this process, including Database Migration Assistant (DMA), Azure Data Studio, Azure Migrate, and Azure Database Migration Service (DMS). The source VMs are running across various OS versions—Windows Server 2008, 2012, 2016, and newer. However, I’ve noticed that DMA appears to be deprecated, and Azure Data Studio is scheduled for retirement by February 2026.
LAB: Set up DR for SQL in Azure VM by using Always on feature
Why create DR for SQL in azure VMs? Creating a disaster recovery (DR) plan for SQL Server in Azure Virtual Machines (VMs) is crucial to ensure business continuity and data protection. Azure VMs offer flexible and scalable solutions for high availability and disaster recovery, such as Always On availability groups, failover clustering, and geo-replication. These features help minimize downtime and data loss during unexpected events, ensuring that your SQL Server databases remain accessible and resilient. By leveraging Azure's built-in DR capabilities, organizations can meet their recovery time objectives (RTO) and recovery point objectives (RPO), safeguarding critical business operations. Architectural diagram Steps Create two SQL Server VM, one for on-premises and another for azure (for sake of lab I am creating both in azure vm. The experience is same for both scenario) Follow the below steps in both SQL VMs to prep for DR. Set domain for sql servers Restart VM (Very Important to make changes effective) Make sure the sql servers are joined to same domain system--> Advanced setting--> computer name-->Change domain Restart VM Create Secondary VM using SQL supported image ( I am selecting standard SQL edition option) Add roles and features In Features select Failover clustering Complete installation Enable Always on feature Repeat step for both VMs Create a primary db in SQL1 In primary create test database and add data -- Create the database CREATE DATABASE userdatabase; -- Switch to the new database USE userdatabase; -- Create the table CREATE TABLE userinfo ( email VARCHAR(255) NOT NULL, name VARCHAR(255) NOT NULL ); -- Insert dummy data into the userinfo table INSERT INTO userinfo (email, name) VALUES ('john.doe@example.com', 'John Doe'); INSERT INTO userinfo (email, name) VALUES ('jane.smith@example.com', 'Jane Smith'); INSERT INTO userinfo (email, name) VALUES ('alice.jones@example.com', 'Alice Jones'); INSERT INTO userinfo (email, name) VALUES ('bob.brown@example.com', 'Bob Brown'); SELECT * from userinfo Create cluster Create Availability group Now you can see both servers are part of same availability group test failoverRegister now for the Migrate to Innovate Summit
Join the summit on March 11, presented in partnership with Intel. Stay agile, innovate for the future, and maintain a competitive edge by accelerating your cloud migration and modernization journey. Microsoft thought leaders will discuss the latest news and trends, showcase real-world case studies, and share how Azure can help you fully embrace AI. Join us to: Maximize business value and build the foundation for successful innovation by leveraging the latest Azure and Intel capabilities for your workloads. Dive into case studies and real-world examples showcasing how organizations have successfully transformed their business and how you can be next by migrating and modernizing on Azure. Make sure your cloud migration and modernization journey is using the best practices and strategies featured in product demonstrations. Register now > Migrate to Innovate Summit Tuesday, March 11, 2025 9:00 AM–11:30 AM Pacific Time (UTC-7)
Migrating Windows Server from 'Hybrid Azure AD Join' to 'Entra ID Join (Cloud-Only)'
Hi everyone, I need help with a scenario where I’m looking to move a server ( non DC ) from Microsoft Entra Hybrid Joined to cloud only (Entra ID) Joined only. The goal is to stop relying on the on-premises AD domain and make the server authenticate only through cloud-based accounts (Azure AD accounts). I’d appreciate any guidance, documentation or best practices on how to properly handle this migration while ensuring minimal disruption. Has anyone done this transition before? What steps and considerations should I be aware of in terms of network configuration, Cost.... etc? Thanks in advance for your help!
Invalid Storage Account
I’m trying to migrate a Resource Group across subscriptions but one VM in particular throws up this error The Move Resources request contains VMs which are associated with invalid storage accounts. Please check details for these resource ids and referenced storage account names. (Code: MoveResourcesHaveInvalidState, Target: Microsoft.Compute/virtualMachines) Storage Account 'storageaccountname' either does not exist or is in an invalid state. (Code: MoveResourcesHaveInvalidState, Target: /subscriptions/subscriptionID/resourceGroups/RGName/providers/Microsoft.Compute/virtualMachines/ The referenced storage account does not exist and I have cycled the options on the boot diagnostic storage account to no avail
