Update troubleshoot-missing-environments.md to add env picker missing info

Author: saminyrmalik

support/power-platform/dataverse/environment-app-access/troubleshoot-missing-environments.md

@@ -37,7 +37,7 @@ This table lays out the unique requirements that must be met for an environment
 |Product experience   |Inclusion rules   |
 |---------|---------|
 |Power Platform admin center environment list      | Users must have administrative access to the environment for the environment to show up in the main Power Platform admin center environment list (System Administrator role in Dataverse, Environment Admin role for environments without Dataverse). Power Platform admins, delegated admins, and authorized service principals will see all environments in the tenant. Dynamics 365 admins are limited to seeing environments in which they're a member of the environment security group, if one has been applied.         |
-|Power Apps maker portal environment list      | The environment list in the Power Apps maker portal includes all environments in which the user has been assigned the Environment Maker role plus any environments in which the user has maker permission to one or more apps. **Note**: Assignment of the Environment Administrator role or any custom role doesn't cause the environment to be included in the environment list in the maker portal.         |
+|Power Apps maker portal environment list      | The environment list in the Power Apps maker portal includes all environments in which the user has been assigned the Environment Maker role plus any environments in which the user has maker permission to one or more apps. **Note**: Assignment of the Environment Administrator role or any custom role doesn't cause the environment to be included in the environment list in the maker portal. The environment picker only recognizes users who are members of Microsoft Entra group teams and users who have security roles assigned to them directly.|
 |Power Automate portal environment list      | The Power Automate portal includes environments in which the user has any built-in security role plus any environments in which the user is a co-owner of one or more flows.         |
 
 > [!NOTE]