Skip to content

Commit 409c775

Browse files
committed
image processing
1 parent 1ee583f commit 409c775

File tree

4 files changed

+1
-3
lines changed

4 files changed

+1
-3
lines changed
571 Bytes
Loading
651 Bytes
Loading
Binary file not shown.

azure-local/oem-license.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Azure Stack HCI OEM license overview
33
description: Learn about the Azure Stack HCI OEM license, its benefits, license requirements, activation, and more.
44
author: ronmiab
55
ms.topic: overview
6-
ms.date: 10/21/2024
6+
ms.date: 12/31/2024
77
ms.author: robess
88
ms.reviewer: alkohli
99
# customer intent: As a content developer, I want to provide customers with the appropriate Azure Stack HCI OEM license information so that they can have a clear understanding of what the license is and how it can be beneficial to them.
@@ -78,8 +78,6 @@ For information on activating AKS, see [Azure Kubernetes Service on Azure Local]
7878

7979
When a cluster or system uses different hardware models, operating system versions, or billing models this is known as a mixed-node scenario. Specifically for OEM license, if your cluster includes a mixed-node scenario where one or more of your machines don't have the OEM license, a notification in your monthly billing status details appears.
8080

81-
:::image type="content" source="media/oem-license/warning-mixed-node.png" alt-text="Screenshot of a warning for a cluster with an unsupported mixed-node scenario." lightbox="media/oem-license/warning-mixed-node.png":::
82-
8381
***We have detected mixed nodes in your cluster. You will be billed monthly for each node in your cluster as one or more servers in your cluster do not have an OEM license. To see which servers do not have the OEM license, go to Overview > Nodes and check the OEM license column. Learn more.***
8482

8583
> [!NOTE]

0 commit comments

Comments
 (0)