Windows Configuration Designer - Enroll in Azure AD - Bulk token retrieval failed: Bad Request

Arend Dieperink 0 Reputation points
2023-09-20T12:17:57.4533333+00:00

I am attempting to create a Provisioning Package for Bulk enrollment.

When I run the WCD and 'Get Bulk Token', I get the following error:
'Bulk token retrieval failed - Bad Request'

The Windows device is Windows 10 build 22H2 - Hybrid Joined.

The account used to retrieve the Token is Global Admin and Local Admin.

The account is licensed with M365 Business Basic / Enterprise Mobility and Security E3.

MDM & MAM User Scope are set to 'All'

Microsoft Security | Microsoft Entra | Microsoft Entra ID
Windows for business | Windows Client for IT Pros | User experience | Other
{count} votes

2 answers

Sort by: Most helpful
  1. Arend Dieperink 0 Reputation points
    2023-09-22T08:22:44.5033333+00:00

    This has been resolved. The issue ended up being related to the account being used for WCD. It had a 'Business Basic' and a 'Enterprise Mobility & Security E3' license. I changed it to 'Business Premium' which then allowed Token retrieval.
    I did however find an excellent post with an PowerShell method for Token retrieval for anyone else that is struggling with the WCD app.
    https://oofhours.com/2023/02/14/simplify-the-process-of-generating-an-aad-bulk-enrollment-provisioning-package/

    0 comments No comments

  2. Marilee Turscak-MSFT 37,206 Reputation points Microsoft Employee Moderator
    2023-10-13T16:17:58.29+00:00

    @Arend Dieperink ,

    I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to "Accept " the answer.

    Issue:

    When running the WCD and "Get Bulk Token", you received the following error:
    'Bulk token retrieval failed - Bad Request'

    Solution:

    The issue was due to the license assigned to the account being used for WCD. It had a Business Basic and an Enterprise Mobility & Security E3 license. You changed it to 'Business Premium' which then allowed Token retrieval.

    You also found a useful resource with a PowerShell method for Token retrieval which may help with others struggling with the WCD app.
    https://oofhours.com/2023/02/14/simplify-the-process-of-generating-an-aad-bulk-enrollment-provisioning-package/

    Please remember to "Accept Answer" if any answer/reply helped, so that others in the community facing similar issues can easily find the solution.

    0 comments No 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.