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.
Sending the user an email with guidelines on connecting before their Cloud PC is ready could lead the user to try to connect before the Cloud PC is ready. Wouldn’t it be cool if a user only gets an email when their Cloud PC is provisioned and ready to use? in my mind, that is the optimal way of giving the information. I will go through the aspect of how this is working.
Knowing how often users connect to their Cloud PC gives you an idea if they are using it or not. From here, you can investigate if there is a reason for a user not to use the Cloud PC as first intended. Ultimately you can track down the users who no longer need a Cloud PC and can save that license cost. as you might know, there is no built-in usage report in the MEM portal. Therefore I have cooperated with Donna Ryan on a PowerShell script that will gather information about login count over a period and the last login date.
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.
When a user is logged into their Cloud PC, non-admin users cannot see the Restart button in the power menu. Therefore they can only restart their Cloud PC from the Windows 365 web interface. I don’t think this is an issue if users only use the Windows 365 web interface. However, I see a “user experience” issue if they are using the Remote Desktop Client instead.
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?
Microsoft has done it more straightforward to export Azure Role Assignments for a subscription. They have added the Download role assignments button in the Azure portal under Subscriptions. However, when I’m working with customers with many Subscriptions, I’ll like to get an overview of all the subscriptions at once. Therefore I use PowerShell the export Role Assignments for all Subscriptions at once.
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 »
Azure provides a simple way to connect on-premise workstations to Azure resources like VM and other services with a Point-To-Site VPN. This can be really handy if you have some external partners that need to connect to your environment in Azure, or just have a couple of users that needs special access to some services… Read More »