[CoE Starter Kit - BUG] Inventoring issue with Microsoft 365 environment

[fim34]

Does this bug already exist in our backlog?

• I have checked and confirm this is a new bug.

Describe the issue

Hello,

A new Microsoft 365” environment appeared in tenant on 27/03/2025.
It seem with environment was created by design as part of a new Copilot feature called Scheduled Prompts. When a user with a valid Copilot license uses Scheduled Prompts for the first time, the Microsoft 365 environment is automatically created in the background. This ensures that required solutions, such as:

• M365 Copilot Actions Solution
• M365CopilotAutomations Solution

These are provisioned and ready to support the Copilot features.

If the environment is deleted and Scheduled Prompts are used again, it will be automatically recreated.

Needed to be global admin to add myself as system admin and add the service account who run the flow inventory.
But still issue for this environment with error

The user with object id 'its service account' in tenant '' does not have access to permission 'ManageAnyCustomApi' in environment 'id of microsoft 365'. Error Code: '<null>'

So what is missing on this environment to remove this error we have , its only on one flow who want to check this environment.

Regards

Expected Behavior

No response

What solution are you experiencing the issue with?

Core

What solution version are you using?

4.47.1

What app or flow are you having the issue with?

CLEANUP HELPER - Check Deleted v4 (Custom Connectors)

What method are you using to get inventory and telemetry?

Cloud flows

Steps To Reproduce

1.need copilot licence
2.Schedule Prompts in copilot portal
3.check ppac to check the environment is created in backend
4. add yourself as admin system and add service account who run the flow
5. wait for the error

Anything else?

No response

[RajeevPentyala]

@fim34 We need to check this scenario at our end. Can you please confirm if the Dataverse provisioned on the created environment?
Meanwhile, if managing this environment isn't essential, consider excluding it from inventory scans to prevent related errors.

[fim34]

Yes there is a dataverse to this environment.
Yes for now we can exlude it, which flow and parameter to modify to exclude the environment ?

[tomka75]

@fim34 Set flag "Excuse From Inventory" for that environment in the table "Environment" to true:

[tomka75]

And I have the same error in the flow "Admin | Sync Template v4 (Custom Connectors)" with the permission "ManageAnyCustomApi" with Core Components version 4.48.3.

[Steven-Hutchens-SKY]

I have the same issue with "Admin | Sync Template v4 (Custom Connectors)" with the permission "ManageAnyCustomApi" with Core Components version 4.48.3.

Error message - Action 'Get_Custom_Connectors_as_Admin' failed: The user with object id 'Service-Account-GUID' in tenant 'Tenant-GUID' does not have access to permission 'ManageAnyCustomApi' in environment 'Environment-GUID'. Error Code: ''

403 Forbidden

It suggests that the service account I'm using doesn't have access to the Environment or Role and it has full Power Platform Admin

[RajeevPentyala]

@Steven-Hutchens-SKY Issue appears to be related to permissions.
To help isolate it, Can you please create a test flow with the Get Custom Connectors as Admin action, using the same connection reference as in the Admin | Sync Template v4 (Custom Connectors) > Get Custom Connectors as Admin action?. Let us know the outcome.