This warning will be shown on the Azure portal for the Azure VM, if the VM was only shut down from within the VM via the RDP session. The second step to totally shut down the VM, is to go to the Azure portal and choose the Stop option at the top of the Essentials blade or use PowerShell to stop the machine. This will deallocate the VM, and incur no more compute charges.
We’ve deployed Azure W10/W2016 VMs where the Network Profile Type is Public. This is not a default setting so not sure why this happens – but this article shows how to change the Network Profile to Private using the Local Security Policy editor.
1.Open the Local Security Policy editor: Run > secpol.msc
The client company is in the process of moving fully to Azure from their physical servers hosted in datacentres. Their favoured web-based file manager GleamTech’s FileVista cannot yet be hosted as an Azure App Service. Until it can be hosted as an Azure App Service, an Azure VM is required to host FileVista. FileVista, ver 7.6+, is able to connect to mapped networks drive via SMB 3.0 to root folders of company data sitting in Azure File Storage. (FileVista does also connect easily to Azure SQL database, but in this case, an Azure WS2016 VM with SQL Server Express and IIS installed is the hosting plan.)
In a previous blog, we noted that remote users of the company were unable to connect from their W10 laptops, into Azure File Storage services, because their ISPs were blocking Port 445, required for SMB 3.0 transmission. FileVista web-based file manager to the rescue!
- Create an Azure WS2016 VM with SQL Express (and SSMS) with 1 additional attached data disk; with a Static IP address & Network Security Group Inbound Rules for HTTP & HTTPS. RDP into the VM to add IIS Role and features; add Inbound & Outbound Port 80 & 443 in Windows Firewall.
- Install, configure & customize FileVista, after creating the new website.