Could chime in here as well.
Same environment displayName with , created by System and the account initiated that activity does not have any Azure AD administrative role assigned.
Has happened now again, after we actively have deleted the environment - only difference is the account which is shown within the recent operations as 'initiated by'
Neither any Canvas App or Cloud Flow is created within.
System Administrator needs to be added to the environment manually by a Service Administrator to gain access, means not even the expected Azure AD administrative roles, which are usually added by default and granted direct environment permission roles are present.
My assumption is that this activity is related to Copilot Studio, but have not managed yet to get any further details.
<edit 7th of July>
@Aikuido2,
@Dido
I am unsure if you are still chasing this topic, but my initial assumption seems to have been right.
This environment is provisioned by default to host runtime for scheduled prompts.
see:
https://learn.microsoft.com/en-us/copilot/microsoft-365/scheduled-prompts-environment
</edit>
Reason for my assumption:
Upon checking the org teams I could see three access teams and one owner team.
All of those access teams relate to 'Internal Microsoft Copilot Studio Chatbotuser team for component collection {some GUID}
The owner team shows the following description: 'Internal power virtual agents Chatbotmanager team for botId {some GUID}'
