You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
No response
Describe the solution you'd like
I have been looking at the fields in the admin_environment table and have not seen that there is a field for the security group to which the environment belongs.
I have checked in Power Automate that the "List Environments as Admin" action does provide this information in a Guid (properties/linkedEnvironmentMetadata/securityGroupId). I think it would be interesting to have this field in the table and if it is possible to store the name of the security group, all the better
Describe alternatives you've considered
No response
Additional context?
No response
AB#2040
The text was updated successfully, but these errors were encountered:
@Titoleto This has been fixed in the latest release. Please install the latest version of the toolkit following the instructions for installing updates. Note that if you do not remove the unmanaged layers as described there you will not receive updates from us.
@Titoleto This has been fixed in the latest release. Please install the latest version of the toolkit following the instructions for installing updates. Note that if you do not remove the unmanaged layers as described there you will not receive updates from us.
Is your feature request related to a problem? Please describe.
No response
Describe the solution you'd like
I have been looking at the fields in the admin_environment table and have not seen that there is a field for the security group to which the environment belongs.
I have checked in Power Automate that the "List Environments as Admin" action does provide this information in a Guid (properties/linkedEnvironmentMetadata/securityGroupId). I think it would be interesting to have this field in the table and if it is possible to store the name of the security group, all the better
Describe alternatives you've considered
No response
Additional context?
No response
AB#2040
The text was updated successfully, but these errors were encountered: