[CoE Starter Kit - BUG] Installing Multiple CoE Environments and Isolating the Makers M365 Group

Does this bug already exist in our backlog?

[X] I have checked and confirm this is a new bug.

Describe the issue

I'm testing out installing multiple production CoE environments that all look at different environment subsets across the tenant. The challenge I am experiencing is that even when I configure environment variables to not do a full inventory, I am still seeing every environments owner getting added to the Makers table and the M365 Makers group, regardless of whether those environments are marked excused or active.

The desired behavior is to have logically separate M365 Makers groups so that we can isolate the M365 Makers group membership to just owners and makers of each subset of environments for each CoE subset.

Expected Behavior

No response

What solution are you experiencing the issue with?

Core

What solution version are you using?

4.31

What app or flow are you having the issue with?

Admin | Sync Template v4 (Driver)

What method are you using to get inventory and telemetry?

Cloud flows

Steps To Reproduce

Install and configure a new CoE environment with the following environment variables,

ProductionEnvironment set to 'yes'
is All Environments Inventory set to 'no'
FullInventory set to 'no'

Wait for the first inventory to complete.

At this point, all environment owners are added to the Makers table and the M365 Makers group.

The challenge with this is if a customer wants to have different production CoE instances for subsets of environments, this means the owners are included in each CoE M365 Makers group, regardless of whether that environment is excused or active in the CoE Inventory Environment.

Anything else?

No response

AB#3348

microsoft / coe-starter-kit