Share via

Activating benefit of Azure Arc enabled Windows Server 2012 R2 failed

Chengzhi Zhang 15 Reputation points
2024-12-04T03:08:22.62+00:00

Activation failed

Activation of Software Assurance benefits for 1 machines has failed with error 'Pay-As-You-Go Subscription for SoftwareAssurance is ineligible due to 'InvalidLicenseStatus'.'

Azure Arc
Azure Arc
A Microsoft cloud service that enables deployment of Azure services across hybrid and multicloud environments.
456 questions

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Chengzhi Zhang 15 Reputation points
    2024-12-04T06:04:19.01+00:00

    We have been informed that this is a known issue affecting all Windows 2012 R2 servers and may also impact other Server editions earlier than Server 2025. This issue is due to the way it is processed by the Azure Arc connected machine agent version 1.47 for Windows Server operating systems prior to Windows Server 2025.

     

    However, I have also been informed that a fix for this issue is pending in the 1.48 release of the Azure Connected Machine Agent, which is expected in January 2025 after the change freeze.

    2 people found this answer helpful.
  2. Q&A Assist
    2024-12-04T03:08:22.6666667+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The error message you encountered, "Pay-As-You-Go Subscription for Software Assurance is ineligible due to 'InvalidLicenseStatus'," suggests that there may be issues with the licensing status of your Azure Arc-enabled Windows Server 2012 R2 machine. Here are some steps you can take to troubleshoot this issue:

    1. Verify License Status: Ensure that the Azure Arc-enabled server is officially licensed through a valid licensing channel. Unlicensed servers are not eligible for Software Assurance benefits.
    2. Check Connectivity: The server must be connected to Azure Arc for enrollment in benefits. Ensure that the server is not disconnected or expired.
    3. Agent Version: Confirm that the Connected Machine agent is version 1.34 or higher, as this is a requirement for Azure Arc-enabled servers.
    4. Core Minimums: If you're attempting to provision Extended Security Updates (ESU), verify that you have specified sufficient cores for the ESU license. Physical core-based licenses require a minimum of 16 cores per machine, and virtual core-based licenses require a minimum of 8 cores per virtual machine.
    5. Permissions: Make sure you have sufficient permissions (Contributor role or higher) within the scope of ESU provisioning and linking.

    If these conditions are met and the issue persists, you may need to consult Azure support for further assistance.

    References:

    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.