but very complicated for elderly and not english speaking persons to understand and realize. Would be a very good idea, mobilizing the elder generation to enhance their internet skills with multilingual and knowledgeable supports. I guess that RDS gives lot of opportunities to create a big future (for all of us)

سرور ویندوز

When I deploy my RDS env, the RDS GW has a fixed public IP but I want my session host to share the same outgoing public IP. This is because some Azure Service such as Azure MySQL only whitelist certain IP.

This is a prevalent requirement, I had been surprised that the AZ std RDS env build docs did not address this RDS.

I am trying an Azure Loadbalancer to achieve this:
https://docs.microsoft.com/en-us/azure/load-balancer/configure-load-balancer-outbound-cli
https://docs.microsoft.com/en-us/azure/load-balancer/load-balancer-outbound-rules-overview

Hope you can put this in the documentation at least put in the "Note" part.

I'd like to join all of my on-premise machines to Azure AD (and remove them from the local domain). However, it is procedures such as this one that are incredibly complex to set up. I'd like to recommend that Azure engineers refine and simplify such a process as this.

https://docs.microsoft.com/en-us/windows-server/administration/hybrid-cloud-print/hybrid-cloud-print-deploy

The easier you make doing a task such as this one, the quicker folks like me will migrate users over to Azure. It should not be so difficult to implement something so basic such as accessing an on-premise printer (that's joined to a local domain) from AAD joined machine.

A new separate page for those of us migrating from Windows Server 2016 to Windows Server 2019 using AZURE. I have not found any helpful information to perform this task.

Always ON VPN with Azure AD

{Multiple CPU interfaces competeing for cluster connection blocking the other like WW3!games
"resource": loyaltyclass Resource
}accessPort.Host@connection.networks\firewall:securities,default-configurations

GOOD AZURE
NIRBHAY

Microsoft should strongly consider implementing support for Azure AD join in future builds of Windows Server 2016. I how a couple of customers that have nearly finished the transition to all cloud and is left with a couple of servers due to legacy software. They are currently left with the option to deploy Azure AD Domain Services for supporting a couple (2-5) servers.

We pay $2k a month for an NVIDIA vGPU instance only to have DX Diag force us to a Microsoft Basic Display adapter.

End this.

Partners like SoftNAS and Nasuni allow you to connect to Azure BLOB storage and share it as a disk. This allows for massive scalability. Unfortunately, these are very expensive solutions when we are just looking for a simple, massively scalable Windows File Server. Please add the ability to mount BLOB (thin provisioned) to a Windows Server VM in Azure and share that capacity. (Either that or enhance Azure Files to more than 5TB and add NTFS permissions).

The ability to move hyperv workloads or replicate AD objects to azure directly from the GUI without additional tools