Error Provisioning the Identity Framework - Invalid Tenant?

[lookitskris]

I'm trying to deploy this SDK from scratch, and failing at the first hurdle with the "Provisioning the Identity Framework" step.

Following the quick start, I've setup and configured everything up to running the run.sh command, and I get the following error:

Logging into B2C tenant asdktestprd9.onmicrosoft.com.
You are not currently logged in to the Azure B2C tenant: asdktestprd9.onmicrosoft.com.
Please be patient, it sometimes take a little while for the login prompt to appear...
You must be logged into your Azure B2C tenant to continue.
Failed to resolve tenant 'asdktestprd9.onmicrosoft.com'.

Error detail: {"error":"invalid_tenant","error_description":"AADSTS90002: Tenant 'asdktestprd9.onmicrosoft.com' not found. Check to make sure you have the correct tenant ID and are signing into the correct cloud. Check with your subscription administrator, this may happen if there are no active subscriptions for the tenant. Trace ID: e377eaa1-fa97-451e-830d-5225308b5e00 Correlation ID: 021227c3-78e9-41dd-b235-eeae3208056e Timestamp: 2024-07-09 14:05:00Z","error_codes":[90002],"timestamp":"2024-07-09 14:05:00Z","trace_id":"e377eaa1-fa97-451e-830d-5225308b5e00","correlation_id":"021227c3-78e9-41dd-b235-eeae3208056e","error_uri":"https://login.microsoftonline.com/error?code=90002"}

### Critical Error ###
Login failed. Please re-run deployment script to try again.

### Critical Error ###
Azure B2C app registrations failed.

### Critical error ###
Configuration of Azure B2C tenant failed.

During the process, before key vault was created, I was asked to login via https://microsoft.com/devicelogin with a code, and that worked for it to progress,

For this Azure B2C tenant, I am not even being asked to login to anything, and the sub/tenantId must be correct as the earlier resources were created successfully?

What am I missing here? Do I need to manually create a B2C Tenant before attempting this?

Thanks

[lookitskris]

I saw the answer wanyeki gave in another post here about updating cli versions, and that seems to have fixed this issue - thanks