В 2017 году Microsoft анонсировала работы по разработке бесплатного HTML5 веб-интерфейса для администрирования и централизованного управления серверами Windows Server. Проект получил кодовое название Project Honolulu. В апреле 2018 года Microsoft выпустила RTM решение и теперь данный продукт официально называется Windows Admin Center.
Идея Microsoft заключается в замене традиционных MMC консолей и других графических инструментов управления серверами Windows возможностью управления из браузера через единый веб интерфейс (по аналогии с веб-клиентом управления VMware vCenter). Admin Center разворачивается локально и может быть использован в том числе для управления серверами, изолированных от Интернета.
На данный момент проект Гонолулу находится в стадии preview и доступен как часть программы Windows Server Insider. В текущей версии из веб-интерфейса возможно выполнить около 80% типовых задач администрирования серверами Windows Server. По информации от Microsoft, RTM версия продукта будет доступна в марте 2018 года (вместе с выходом обновления 1803).
Содержание:
- Особенности, требования и ограничения Windows Admin Center
- Установка Windows Admin Center в Windows 10/ Windows Server 2016
- Использование консоли Admin Center для управления серверами Windows
Особенности, требования и ограничения Windows Admin Center
Windows Admin Center поддерживает управление следующими версиями ОС: Windows Server 2016, Windows Server 2012 / R2, Hyper-V 2016/2012R2/2012, Windows 10, северами Azure, а также Core редакциями. Возможно также управление целыми кластерами: Failover Clusters, Hyper-V Clusters и виртуальными машинами Hyper-V на них.
На управляемый хост не нужно устанавливать никаких агентов или дополнительных расширений. Коммуникация осуществляется выполняется через Remote PowerShell и WMI over WinRM с помощью RESTful API. На управляемых серверах должен быть установлен как минимум Management Framework (WMF) 5.0 (Powershell 5.0). На Windows Server 2012 / R2 WMF 5.0 нужно становить отдельно.
Узнать поддерживаемую версию Powershell можно с помощью команды:
$PSVersionTable
Сам веб интерфейс Windows Admin Centerнаписан на HTML 5 и корректно работает в Edge и Chrome (Internet Explorer пока полностью не поддерживается).
В последней доступной версии Windows Admin Center прямо из окна браузера поддерживается RDP подключение через веб-интерфейс и консоль PowerShell.
На Windows Server 2016 можно установить Windows Admin Center в режиме шлюза (Gateway Mode), в этом режиме возможно удаленно подключаться к консоли управление с других компьютерах. На Windows 10 / Windows Server 2012 клиент устанавливается в режиме Desktop Mode (консоль доступна только с локального компьютера).
Для авторизации на удаленных серверах можно вручную вводить данные для авторизации, или использовать Local Administration Password Solution (LAPS).
Установка Windows Admin Center в Windows 10/ Windows Server 2016
Установить Windows Admin Center можно на Windows 10 или на Windows Server (2016 и 1709) в режиме Gateway. Чтобы скачать msi дистрибутив Windows Admin Center (около 30 Мб), можно на странице https://docs.microsoft.com/en-us/windows-server/manage/windows-admin-center/understand/windows-admin-center
Установить дистрибутив Windows Admin Center можно из командной строки (с самоподписанным сертификатом сроком действия 60 дней)
msiexec /i HonoluluTechnicalPreview1712-05002.msi /qn /L*v log.txt SME_PORT=6516 SSL_CERTIFICATE_OPTION=generate
Либо с помощью обычного мастера установки. По умолчанию для управления используется порт 6515 (можно изменить). На Windows Server компонент Admin Center устанавливается в виде отдельной службы.
После установки веб интерфейс консоли Honolulu можно открыть, перейдя по адресу:
https://ip_сервера:6516
или с помощью значка на рабочем столе.
Использование консоли Admin Center для управления серверами Windows
По умолчанию в веб-консоли добавлен только один локальный сервер.
С помощью кнопки Add можно добавить
- Отдельный сервер (Server Manager)
- Отказоустойчивый кластер (Failover Cluster Manager)
- Кластер Hyper-V (Hyper-Converged Cluster Manager)
В нашем случае у нас только один сервер. Выберем его, чтобы открыть веб консоль управления. На этой странице отображаются характеристики сервера, а также его состояние в реальном времени (производительность, нагрузка и т.д.). прямо из этой панели можно выключить или перезагрузить сервер, изменить его имя.
В левом сайдбаре представлен список доступных функций, которыми можно управлять из веб-интерфейса. Кратко пробежимся по основным:
Список возможностей веб консоли Windows Admin Center пока не дотягивает до полноценного функционала всех инструментов управления Windows, однако со временем доступный функционал веб интерфейса будет существенно расширен. В дальнейшем Microsoft планирует опубликовать SDK, позволяющий партнерам расширять функционал консоли Admin Center.
Introduction
Windows Admin Center (WAC) is a powerful, web-based management tool designed to simplify and enhance the administration of Windows Server environments. It provides an interface for managing servers, clusters, and hyper-converged infrastructure, all from a single location.
In this guide, we’ll walk you through the installation process for Windows Admin Center on Windows Server, covering everything from initial setup to configuration.
Server Manager vs. Windows Admin Center
When it comes to managing Windows Server environments, both Server Manager and Windows Admin Center (WAC) offer powerful tools, but they serve different purposes and provide distinct advantages.
Server Manager
Server Manager has been the primary tool for managing server roles and features. It provides a centralized dashboard for installing and configuring server roles, monitoring server performance, and managing local and remote servers. Its strengths lie in its direct integration with Windows Server and its ability to manage multiple servers from a single console. However, Server Manager can be limited in functionality when dealing with complex or large-scale environments.
Windows Admin Center
Windows Admin Center represents a more modern approach to server management, offering a comprehensive web-based interface that goes beyond the capabilities of Server Manager. WAC allows administrators to manage servers, clusters, and hyper-converged infrastructure through a single, unified console accessible from any web browser.
WAC also provides advanced features like real-time monitoring, in-depth diagnostics, and seamless integration with Azure services. Additionally, WAC supports management of both physical and virtual environments, making it a versatile choice for diverse IT infrastructures.
In short, Windows Admin Center provides a more advanced, flexible, and comprehensive solution for modern IT environments.
Installation Options and Types
Windows Admin Center (WAC) offers flexibility in its installation, allowing you to choose the best setup for your environment. Understanding the available options and types will help you select the most appropriate configuration for your needs.
Installation Options
- Install on Windows Server: This is the most common approach, particularly for organizations that need centralized management of Windows Server instances. Installing WAC on a Windows Server provides a dedicated management platform, ideal for handling multiple servers and complex environments.
- Install on Windows 10: For smaller environments or individual administrators, WAC can be installed on a Windows 10 machine. This setup allows for management tasks from a client machine and is useful when a dedicated server is not available.
- Azure VM Installation: WAC can also be installed on an Azure virtual machine. This option is beneficial for cloud-based environments, enabling management of both on-premises and cloud resources from a single interface.
Installation Types
- Local Client: This type involves installing WAC on a local machine, such as a Windows 10 or Windows Server. It is suitable for individual administrators or smaller environments where a dedicated management server is not required.
- Gateway Server: Installing WAC as a Gateway Server means setting it up on a Windows Server to act as a centralized management point. This configuration is ideal for larger environments, providing a single interface for managing multiple servers and clusters.
- Managed Server: In this setup, WAC is installed on a server that is also managed through WAC. This approach simplifies management by using the same server for both hosting and managing, though it may not be suitable for high-availability scenarios.
- Failover Cluster: For high availability and fault tolerance, WAC can be set up in a failover cluster configuration. This ensures continuous access to the management interface by providing redundancy and resilience in case of node failures.
Check out this link from Microsoft documentation to learn more abut Installation types.
In this guide, we’ll focus on installing Windows Admin Center as a Gateway Server on a Windows Server, a robust and scalable solution for centralized management in diverse IT environments.
Note
It’s generally recommended to install Windows Admin Center on a Windows Server that is joined to the domain but is not a domain controller. This approach ensures that WAC has the necessary domain credentials and access to manage other domain-joined servers while avoiding potential security and performance issues that might arise from installing it directly on a domain controller.
You can still install WAC on a standalone server. This can be useful for lab setups, non-production environments, like in this guide.
Step-by-Step Installation
Download Windows Admin Center
- Visit official website: visit this link to download the installer
- Choose the Version: Ensure you download the version compatible with your server’s operating system. Check the release notes if you’re unsure which version to choose.
Prepare Your Server
- Update Windows Server: Before installing, make sure your Windows Server is up to date with the latest patches and updates. This can be done via Windows Update or by using WSUS (Windows Server Update Services) if it’s configured in your environment.
- Check System Requirements: Verify that your server meets the minimum hardware and software requirements for Windows Admin Center. Ensure that necessary components like the .NET Framework are installed.
Run the Installer
Double-click the installer to begin the installation process. If prompted by User Account Control (UAC), click “Yes” to allow the installer to run. Follow the Setup Wizard:
Accept the License Agreement: Read through the license terms and accept them to proceed.
Select Installation Type: Choose the “Gateway Server” installation type, as this guide focuses on setting up WAC on a Windows Server for centralized management.
Specify the Port and SSL Certificate: You can use the default port 443 (HTTPS) or choose a custom port. For production environments, it’s recommended to use an SSL certificate from a trusted Certificate Authority (CA). If you don’t have one, you can generate a self-signed certificate for testing purposes.
Complete the Installation: Click “Install” to start the installation. The process may take a few minutes.
See screenshots below:
Another important point to consider is the use of a self-signed SSL certificate when setting up Windows Admin Center (WAC). If you opt for a self-signed certificate, be aware that it will expire in 60 days. Additionally, because the certificate is self-signed by the machine where WAC is installed, other machines on the network will not automatically trust it. This will result in a warning when you try to connect to the WAC site from another device.
In a production environment, it’s recommended to use a certificate issued by a trusted Certificate Authority (CA) on your network. This ensures that the certificate is recognized and trusted by all machines, providing a more secure and seamless experience.
Configure Windows Admin Center
After installation, WAC will launch automatically in your default web browser. You’ll be prompted to complete the initial configuration.
If you want to access WAC later, open your browser and navigate to the server’s address, followed by the chosen port number.
Let’s do some basic configurations for this lab:
Adding Extensions
You can install extensions to extend capabilities of Windows Admin Center (WAC). We will install Active Directory and DNS extensions :
- Click the Settings icon (gear icon) on the top right corner of the WAC dashboard.
- In the left menu, select Extensions.
- In the Available extensions tab, use the search bar to locate the Active Directory and DNS extensions.
- Click Install for each extension to add them to your WAC environment.
See screenshots below:
After installation, return to the Dashboard, select the server you want to manage (dell-host). Under Tools, you’ll now see Active Directory and DNS listed.
Adding Servers
When adding servers to Windows Admin Center (WAC), the servers do not necessarily need to be joined to the same domain, but they do need to be accessible over the network. For instance, servers could be within the same network segment, connected through VPN. Here are the different scenarios:
- Domain-Joined servers: If both the Windows Admin Center gateway server and the target servers are joined to the same domain, WAC can leverage Active Directory for seamless authentication and management
- Workgroup or Standalone servers: If the servers are not joined to a domain, you’ll need to provide the local administrator credentials for each server. Additionally, you might need to configure the server’s firewall and enable certain remote management protocols (like WinRM) to allow WAC to connect and manage them.
- Cross-Domain or Hybrid environment: If servers are part of different domains or a mix of on-premises and cloud-based (e.g., Azure), you can still manage them with WAC as long as network connectivity is established and the necessary credentials are provided.
In this lab example, we are at the scenario where we will add a standalone VM.
Now let’s start managing your servers by adding them to WAC.
- Click on “Add” and enter the names or IP addresses of the servers you want to manage. You can also group servers by roles or functions for easier management. Since it is a standalone server, you will need to use the server IP address.
- Choose “Use another account for this connection” to specify the credentials.
- Enter the local administrator credentials for Server-1 (the username and password you use to log in to the server).
See screenshots below:
Conclusion
Windows Admin Center provides a powerful, centralized interface for managing your Windows Servers, whether they are domain-joined or standalone. By following the steps outlined in this guide, you can easily install WAC and extend its capabilities to effectively manage your infrastructure, ensuring a more streamlined and secure server environment.
Skip to content
Windows Admin Center Part 1 : Overview and Installation
Microsoft unveiled a new tool that is set to change the way Windows Server engineers interface, configure, interact with, and administer Windows Servers, Windows Failover Clusters, and Hyperconverged clusters.
Table of Contents
- Windows Admin Center Overview
- Windows Admin Center Access and Permissions Model
- Installing Windows Admin Center on Windows 10
- Final Thoughts
Microsoft has seen the writing on the wall with new versions of Windows Server as well as the shift to the cloud, administrators need a better tool to be able to take care of the tasks at hand with modern infrastructure that stretches between on-premises and public cloud environments. They have delivered with a new tool that is set to become the de facto GUI administration tool for Windows Server versions to come – Windows Admin Center.
Protect Your Data with BDRSuite
In this Windows Admin Center overview and installation post, we will take a closer look at the tool as well as features and functionality included giving administrators an all-compassing utility to manage Windows Server infrastructure both on-premises and in the cloud.
Windows Admin Center Overview
Windows Admin Center provides tremendous value to administrators.
It started life as Project Honolulu before it was properly named Windows Admin Center and is what Microsoft calls the “evolution” of Windows Server in-box management tools.
It is a free utility available from Microsoft that is available to download at the official Windows Admin Center page here. At the time of this writing, it is available in version 1809.51 in GA form and also version 1902 in Preview.
While Windows Admin Center is not included by default in current Windows Server versions, you can tell that Microsoft is pushing the use of Windows Admin Center. When you launch the legacy “Server Manager” in Windows Server 2019, you will see a message box pop up recommending you try the new Windows Admin Center for server management.
Message in Windows Server 2019 when launching Server Manager recommends trying Windows Admin Center
It provides a single pane of glass management interface that helps administrators to consolidate their view of the Windows Server landscape in their environments. The look and feel of Windows Admin Center are very modern, clean, and intuitive with a very comfortable layout of modules and available actions. This stands in contrast to Server Manager which can be clumsy to maneuver and navigate.
Windows Admin Center is a departure from the standard “fat” application that is loaded on a Windows Server system. It is a browser-based tool that can be loaded not only on Windows Servers but also Windows 10 clients as well.
Additionally, it can also run on Server Core systems as well. It, however, does not require Internet connectivity or an Azure account.
Windows Admin Center can be installed on the following operating systems (***Note*** Installation on Domain Controllers is not supported)
| Windows 10, version 1709 or newer | Desktop mode |
| Windows Server Semi-Annual Channel | Gateway mode |
| Windows Server 2016 | Gateway mode |
| Windows Server 2019 | Gateway mode |
The following operating systems are compatible for management of Windows Admin Center:
| Version | Manage node via Server Manager | Manage cluster via Failover Cluster Manager | Manage HCI via HCI Cluster Manager |
|---|---|---|---|
| Windows 10, version | Yes (via Computer Management) | N/A | N/A |
| 1709 or newer | |||
| Windows Server Semi-Annual Channel | Yes | Yes | N/A |
| Windows Server Semi-Annual Channel | Yes | Yes | N/A |
| Windows Server 2019 | Yes | Yes | Yes |
| Windows Server 2016 | Yes | Yes | Yes, with latest cumulative update |
| Microsoft Hyper-V Server 2016 | Yes | Yes | N/A |
| Windows Server 2012 R2 | Yes | Yes | N/A |
| Microsoft Hyper-V Server 2012 R2 | Yes | Yes | N/A |
| Windows Server 2012 | Yes | Yes | N/A |
| Windows Server 2008 R2 | Yes, limited functionality | Yes | N/A |
Refer this Microsoft article to prepare your environment for Windows Admin Center as some server versions need additional preparation
Windows Admin Center Access and Permissions Model
The two modes that are supported for Windows Admin Center as detailed for the respective operating systems in the above table are:
- Desktop Mode
- Gateway Mode
Desktop Mode
In Desktop Mode, the Windows Admin Center is locally installed on the same computer from which you are accessing it.
An example of a URL to access WAC in this mode is: https://localhost:6516
Gateway Mode
In Gateway Mode, Windows Admin Center is installed on a supported Windows Server version and can be accessed remotely from a client browser on a different machine.
An example of a URL to access WAC in this mode is: https://servername.contoso.com
Access roles can be assigned in the Gateway mode for appropriate permissions. There are two roles for access to the gateway service: gateway users and gateway administrators.
- Gateway users can connect to the WAC gateway service to manage servers through the gateway but cannot change access permissions nor the authentication mechanism used to authenticate to the gateway
- Gateway administrators can configure who gets access as well as how users will authenticate to the gateway
Additionally, role-based access control or RBAC can be used in WAC to provide users with limited access to the machine instead of making them full local administrators. This works in conjunction with configured each managed server with a JEA or “Just Enough Administration” endpoint.
Installing Windows Admin Center on Windows 10
By default, when installed on Windows 10, Windows Admin Center uses port 6516 by default. However, this can be changed. When installed on supported Windows Server operating systems, Windows Admin Center is installed as a network service. A port will need to be specified for listening as well as an HTTPS certificate is required. Self-signed certificates can be used for this purpose, however, all the same certificate best practices apply here and are required including subject name matching the server name, etc.
Installation on Server Core versions is possible as well from the command line. Copy the Windows Admin Center installation MSI over to the Server Core machine and run the following command:
- msiexec /i .msi /qn /L*v log.txt SME_PORT= SSL_CERTIFICATE_OPTION=generate
Installation using the GUI MSI installer is very straightforward. It is very much a “next, next, finish” process.
Beginning the Windows Admin Center installation with EULA
Windows Update settings
Installation options – Gateway Mode for Servers
Allow Windows Admin Center to modify the Trusted Hosts file
Select the Server port and Certificate options
Installation of Windows Admin Center in Gateway mode finishes successfully
After the installation is complete, browse to the URL listed for the new Windows Admin Center installation and login:
Login with credentials to access WAC
After adding servers and even a Hyper-Converged S2D cluster to Windows Admin Center
Windows Admin Center provides a wide range of tools for single servers and clusters:
A look at some of the available tools for a single server
Dashboard metrics for S2D cluster showing issues and pertinent information about the S2D cluster
Final Thoughts
Windows Admin Center is the next step forward for Microsoft and server administration. It provides a clean, modern look and feels for Windows Server and cluster administration. It is a huge step forward when compared to Server Manager and other more legacy tools that we have grown accustomed to. Third-party vendors are also able to extend its capabilities which has already led to some pretty incredible extensions available from various vendors for WAC.
Considering this is a free download from Microsoft and it is able to manage many different types of servers, it is a great tool to start today in managing Windows Servers from in various environments. With the single pane of glass view of the Windows Server and cluster landscape, it allows a centralized management plane for configuring, managing and troubleshooting Windows Server moving forward.
Read More: Server Management with Windows Admin Center
Related Posts
Server Management with Windows Admin Center
Beginners Guide for Microsoft Hyper-V: How to Create a Virtual Switch in Hyper-V using Windows Admin Center – Part 33
Beginners’ Guide for Microsoft Hyper-V: Azure Features in Windows Admin Center – Part 31
Windows Admin Center – Simplified for Beginners
Beginner’s Guide for Microsoft Hyper-V: Managing Windows Server Containers with Windows Admin Center – Part 20
Follow our Twitter and Facebook feeds for new releases, updates, insightful posts and more.
Try BDRSuite for Free!
Schedule a live demo with one of our product experts
Start your full-featured 30-day free trial
Explore detailed pricing, editions & features
Among the many new features announced at Microsoft Ignite, relating to Windows Admin Center, there is the release of vNext (modernized gateway) of the server and client management platform. The reason behind this choice is very simple and dates back to the release of WAC way back in 2018. The product was created to be the evolution of the Server Manager and to evolve two very obsolete tools such as the Failover Cluster Manager and Hyper -V Manager.
Over time, however, Microsoft realized that WAC could become the hub of many other products and integration with Azure. Here come exclusive solutions, such as System Insights and Storage Migration Services which are only available in Windows Admin Center.
Time passes and integration with Microsoft Azure arrives, to activate solutions such as Azure File Sync, Azure Backup, Azure Arc and much more in just a few clicks.
Azure Stack HCI arrives in 2020 and Windows Admin Center is the cornerstone for the creation and management of the Microsoft hyperconvergence platform.
Everything changes but the product behind the scenes does not change, which is starting to be slow to start up, slow to open connections to objects and to provide rapid results. To be honest, this was one of the most discussion point during many internal PGI and MVP Summit.
The product team knows this and starts an optimization process that sees a first step with the arrival of build 2306 and later with 2311, which brings a performance improvement of up to 50% thanks to the use of Angular 15, yet the problem remains.
Windows Admin Center v2
This explains the reason for the new gateway which introduces, at least for now, 4 big new features:
- Upgrade from .NET 4.6.2 to .NET Core
- Updated installer
- Multi-process, micro-service based architecture
- Kestrel HTTP web server HTTP/2
It doesn’t take much to understand that these innovations bring great benefits in terms of performance and back-end operations. Moving to .NET Core and the use a microservices architecture means that multiple tasks can be executed at the same time and a single block can be scaled horizontally. The use of HTTP/2 improves response performance and therefore faster execution times are achieved.
In short, unchanged bodywork but new chassis and engine.
Installation and Configuration
The installation of the product, currently in Preview, is slightly different from the past but what really changes is the management of how the WAC service is published – now you can change the internal and external ports, rather than deciding how to interact at the safety.
The authentication page also changes, to make it clearer than the old Windows authentication.
For now, the graphic interface has not changed, which has already seen an improvement with the 2311, but the performances have changed and are now more in line with user expectations.
Since this is a preview, there are limitations which are mostly related to extensions. In fact, only those created by Microsoft are supported and not all, or rather not the extra ones such as Active Directory, DHCP or DNS.
Good News, Bad News
Where there are still no improvements from virtualization management side. From my point of view, WAC would need an agent to give it a leap in performance and to avoid a continuous refresh of the virtual machines present in the hosts (follow the Virtual Machine Manager concept).
There aren’t too much news in this sense but my suspect is that Azure Arc could become a key element, to fix this gap. In fact, as you know, Arc is now mandatory part of Azure Stack HCI 23H2 and could be used to retrive information from hosts like VMs, storage, monitoring and more. If we try to think about micro-services model introduced, the idea to use a continuous background connection between WAC and Azure Arc is not so strange.
Get Started
Windows Admin Center vNext can be used side-by-side with the standard version but it is recommended to run it in a dedicated VM to avoid problems with the production environment.
To download the preview, you must be registered with the Insider program, available at the following link – Download Windows Server Insider Preview (microsoft.com)
#DBS
What we see these days is that more and more companies embrace, public clouds, like Azure, and start working in a hybrid cloud scenario. Where they not only run their resources and workloads on-premises in their own data centers, but also in Azure or in other public cloud environments, like AWS or Google Cloud.
And this is where Windows Admin Center (WAC) comes into play, because it can not only be used to centrally manage your complete Windows server environment. But next to that it can also be used as a gateway to extend your on-premises servers to the cloud by using all kind of Azure Hybrid Cloud services, like Azure Arc, Azure Monitor or Azure Backup.
To be able to use these Azure hybrid services within WAC, there are some configuration steps you need to complete. First of all, you must register your Windows Admin Center gateway with Azure. For this registration, which you only need to do once, your Windows Admin Center gateway requires an Azure Active Directory (Azure AD) application ID. During this registration, also all the necessary permissions needed to create and manage Azure resources on your behalf will be automatically configured.
In this blog post, I will show you all the required steps you need to follow to register your WAC instance with Azure.
Prerequisites
- WAC (currently version 2110) running on a local Windows Server instance (Windows Server 2019 or 2022) and configured as a Gateway Server. You can download WAC from here.
- The user who registers the gateway needs to have the Windows Admin Center gateway administrator role.
- An Azure Subscription
- An Azure Administrator account
You can find more information about the he different installation options for WAC over here
Registration steps
Open your Windows Admin Center from a web browser, like Edge or Chrome (preferably from a privileged access workstation). When logged in, click on the Settings gear icon, which you can find in the top right corner, to open the Account page.
On the Account page click on Register with Azure.
And then click Register to start registering your WAC with Azure.
On the Get started with Azure in Windows Admin Center page, which opens on the right-side, select Azure Global from the Select an Azure cloud dropdown menu. Then click the Copy button to copy the uniquely generated device code.
Click the Enter the code URL, which will open up another browser window into which you can then paste the code you just copied.
After pasting the code, click Next.
On the Sign in pop-up page you need to enter the credentials to connect your WAC with Azure. So, first of all enter your accounts email address for authentication and then click Next.
Then enter the password for the account and click Sign in.
If MFA is enabled for your account, approve the sign in request with your Microsoft Authenticator app.
When you are asked to confirm that you are trying to sign into Windows Admin Center, click Continue.
If all went well, you then should see the following message: “You have signed in to the Windows Admin Center application on your device. You may now close this window.” If so, close the browser window and return to the original registration page.
Back on the registration page, click Create New under the Azure Active Directory Application field (or select Use existing if you already have an existing Azure AD application ID). Then click Connect, to create a new Azure AD application from which you will be able to manage your gateway user(s) and gateway administrator(s) access.
If your account has the sufficient Azure RBAC role, you should see a confirmation saying: Now connected to Azure AD. If so, select Sign in to sign into Windows Admin Center with your Azure Administrator account.
On the Permissions requested dialog box, click Accept.
If all went well, you should now see that Windows Admin Center is successfully registered with Azure.
You can now also verify your signed in Azure Account or even switch accounts under the Account page.
You can also verify or change any settings for the newly created WAC Azure AD app by login in into the Azure Portal, where you open the Azure Active Directory page. You can then find the WAC Azure AD app under the Manage field, by clicking on App registrations and selecting All applications.
You now have successfully registered your WAC with Azure and you can start onboarding your on-premises servers and start using the available Azure services.
Conclusion
These days you can use WAC to enable all kind of Microsoft hybrid cloud scenarios. To do so, first you will need to register your Windows Admin Center gateway with Azure, which allows WAC to communicate with Azure. Afterwards you can onboard your on-premises or other cloud servers and start using Azure Hybrid features like Azure Backup, Azure Site Recovery, Azure Arc or Azure Monitor directly from inside WAC to manage, backup or better protect them.