Hello Robert, I think this is due to role assignment scope in Azure Role-Based Access Control. Although you have the Lab Creator role, it’s important to note that where the role is assigned matters significantly.
According to Microsoft documentation
Labs don’t inherit any roles assignments from the lab plan. However, role assignments from the resource group are inherited by lab plans and labs in that resource group.

So even if you are a Lab Creator on the Lab Plan, that does not automatically grant access to individual labs, unless your role is scoped to the lab itself or to the resource group that contains the labs.
To resolve this issue and see your labs on labs.azure.com, in your Azure portal, navigate to the resource group that contains your lab. Open Access control (IAM). Click view my access and check if your role (e.g. Lab Creator) is scoped at the resource group or lab level. If it's only assigned at the subscription or lab plan level, it will not propagate to the individual lab. You can either re-assign the Lab Creator role at the resource group level, or assign yourself as Lab Owner/Contributor on each individual lab.
Microsoft’s guide explicitly states-
Grant permission to create or manage your own labs for all lab plans within a resource group which clearly says the role must be scoped at the resource group or lab plan, and not just the subscription
Grant permission to create or manage your own labs for all lab plans within a resource group.

Relevant Microsoft Document for your reference-
- Azure role-based access control - Azure Lab Services | Microsoft Learn
- Assign a lab creator - Azure Lab Services | Microsoft Learn
- How to add a lab creator to a lab account with Azure Lab Services - Azure Lab Services | Microsoft Learn
- Quickstart: Create lab plan resource - Azure Lab Services | Microsoft Learn