I created this post to help you with all the requirements you’ll need to check before working on deploying your Horizon Cloud Next-Generation using Microsoft Azure. Enjoy this step-by-step! Microsoft Azure Subscription Requirements Requirements Checklist for Deploying a Microsoft Azure Edge https://docs.vmware.com/en/VMware-Horizon-Cloud-Service—next-gen/services/hzncloud.nextgen/GUID-63AB2398-E82F-4EF2-BC7F-145D79E28769.html Source: https://docs.vmware.com/en/VMware-Horizon-Cloud-Service—next-gen/services/hzncloud.nextgen/GUID-587457D4-0D6D-413A-96C4-E7B2E8449815.html#GUID-587457D4-0D6D-413A-96C4-E7B2E8449815 Note: Horizon Edge using an AKS cluster requires a user-managed identity with
Category: Microsoft Azure
Hello everybody! I’m glad you’re here again! At this point, you might be aware about your Microsoft Azure access, privileges and you have access to the console within properly roles assigned for you. So let’s check Quota and why is this an important step towards establish your Horizon Cloud on Azure environment. Understanding Quota Quota
If you’re new on Microsoft Azure, you’ll need to have a valid subscription and specific administrative privileges in order to start setting properly your environment to receive Horizon Cloud on Azure. So let’s check what you need to cover: Subscription Everything starts with your Azure Subscription. This is the place where you can put all
Every time I have a conversation with a customer and some times this ends up in a PoC for testing VMware Horizon running on Microsoft Azure, the following documentation is provided with an extended requirements in which customer needs to prepare its environment prior start testing it. Requirements list is well documented on this link.
Ok, so you might be following the steps to configure your first AzureAD Connect using my previous post, Am I right? (If I’m wrong, just click here and check what you’ve missed). Now it’s time to configure your ADFS using Azure AD Connect for Federating Office 365. Let’s check what you need to do. Azure
