For end users to have a good experience interacting with any IT systems these days, Single Sign-On (SSO) is a must-have. I can’t emphasize enough how annoying and non-productive it is to log in multiple times to access corporate resources or systems. When using Azure Virtual Desktop (AVD) or Windows 365, there is no exception configuring SSO is a must.
One of the core elements of Windows 365 is the Reprovisioning feature, which allows IT Administrators to recreate a user’s Cloud PC within minutes. Even though the old Cloud PC is being deleted from Intune, the device object still exists in Azure AD. Because Reprovisioning of Cloud PCs might be done quite frequently depending on how many Cloud PCs and issues the users face. The number of device objects in Azure AD might increase quite fast.
Resizing a Windows 365 Enterprise Cloud PC is very easy and can be done directly within the MEM portal. I like this feature and how seamless it’s working. However, we cannot resize our Cloud PC if we have assigned the license through group-based licensing.
Group-based licensing is a must to gain better visibility and control of your licenses. Therefore it’s a big issue if you ask me.
This article will showcase the PowerShell script I have created to resize group-based licensed Cloud PC.
If you manage Active Directory, Windows Server deployment, or something else, PowerShell is an essential tool to master. When it comes to Windows 365, there is no difference. The capability to deploy or get information on environments is handy, especially if you want to automate something.
This article will go through how to get information about your Windows 365 environment with PowerShell. But how is it possible when there is no PowerShell module for Windows 365?
A guide on how to prepare a resource migration between Azure subscriptions. This will give you an idea of approaching a resource migration project and validating if your source environment can run on your destination environment. There are serval things to be aware of.
If you deploy an Azure Virtual machine(VM) into a wrong Azure virtual network(Vnet) or you would like to move an existing VM to another Vnet, you will need to deploy a new VM into that Vnet. unfortunately, we can’t move Azure VM’s between Vnet’s, out of the box. You can, of course, establish Vnet peering… Read More »