Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CoE Starter Kit - Feature]: Saving the security group associated with an environment in Dataverse #7460

Closed
Titoleto opened this issue Jan 15, 2024 · 6 comments
Assignees
Labels
coe-starter-kit CoE Starter Kit issues enhancement New feature or request officehourTHANKS

Comments

@Titoleto
Copy link

Titoleto commented Jan 15, 2024

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

@Titoleto Titoleto added coe-starter-kit CoE Starter Kit issues enhancement New feature or request labels Jan 15, 2024
@Jenefer-Monroe
Copy link
Collaborator

This is a great idea! I'll see if I can get this in for the next release.

@Jenefer-Monroe
Copy link
Collaborator

securityGroupId is returned here if there is one.
image

Nothing returned for the field if not
image

Then the securityGroupId mapped straight to O365 Groups
image

@Jenefer-Monroe
Copy link
Collaborator

image

image

image

@Titoleto
Copy link
Author

image

image

image

ohhhh great!!!!

@CoEStarterKitBot
Copy link
Collaborator

@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.

1 similar comment
@CoEStarterKitBot
Copy link
Collaborator

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
coe-starter-kit CoE Starter Kit issues enhancement New feature or request officehourTHANKS
Projects
Status: Done
Development

No branches or pull requests

4 participants