Azure Local: Manage Service Principal through Managed Identity instead of Secret

Сводка: APEX Cloud Platform for Microsoft Azure or old revision of AX product was deployed with Service Principal that used secret for the authentication. However, some customers have high demands for automation requirement, so manually rotating secret from time to time may not fulfill their needs. Microsoft provides Managed Identity using certificates for managing the Service Principal since 23H2. ...

Данная статья применяется к Данная статья не применяется к Эта статья не привязана к какому-либо конкретному продукту. В этой статье указаны не все версии продуктов.
Ознакомьтесь с другими ресурсами

Симптомы

If the Service Principal is using secret to manage the life cycle, after a certain period it expires. After expiration, manual rotation is inevitable.

However, the best practice to manage Service Principal is integrated into Managed Identity instead of secret.

Причина

APEX Cloud Platform for Microsoft Azure started from 23H2. However, its deployment Service Principal still uses the legacy method for authentication which is similar to Azure Stack HCI 22H2.

Some old AX products also faced the same issue.

Разрешение

Reference Microsoft document:
Enhanced management of Azure Local from Azure - Azure Local | Microsoft Learn (External Link)

If the system is already registered to Azure, rerun the registration. Using the RepairRegistration parameter helps configure a managed identity and Azure Service Bus while retaining other information such as resource name, resource group, and other settings.

Register-AzStackHCI  -SubscriptionId "<subscription_ID>" -RepairRegistration
Свойства статьи
Номер статьи: 000434764
Тип статьи: Solution
Последнее изменение: 13 Mar 2026
Версия:  2
Получите ответы на свои вопросы от других пользователей Dell
Услуги технической поддержки
Проверьте, распространяются ли на ваше устройство услуги технической поддержки.