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

Update environment-groups.md #2629

Merged
merged 2 commits into from
May 23, 2024
Merged

Conversation

Jaqiness
Copy link
Contributor

The original documentation does not make it clear that this feature is ONLY for managed environments. My changes improve the clarity of the role of managed environments within this feature.

The original documentation does not make it clear that this feature is ONLY for managed environments. My changes improve the clarity of the role of managed environments within this feature.
Copy link

Learn Build status updates of commit 894888e:

✅ Validation status: passed

File Status Preview URL Details
power-platform/admin/environment-groups.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@@ -43,7 +43,7 @@ Enabling _default environment routing_ might give you more environments to manag

## Create an environment group

[Power Platform tenant administrators](use-service-admin-role-manage-tenant.md) can create as many environment groups as necessary to meet their organization's needs. You can create a single environment group named **Personal Productivity**, then create new developer environments into the group.
[Power Platform tenant administrators](use-service-admin-role-manage-tenant.md) can create as many environment groups as necessary to meet their organization's needs. You can create a single environment group named **Personal Productivity**, then create new managed developer environments into the group.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great addition!


### The sharing limits rule

You can also configure the _sharing limits_ rule. Since the environment group is intended for personal productivity, makers are restricted from sharing their canvas apps with other users. This helps ensure that each environment in the group remains a private space for individual work.
You can also configure the _sharing limits_ rule. Since the environment group is intended for managed personal productivity, makers are restricted from sharing their canvas apps with other users. This helps ensure that each environment in the group remains a private space for individual work.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The prefix "managed" is not appropriate in this sentence. I suggest we keep "personal productivity" all the while including the other changes proposed in this PR.

Copy link
Contributor

@mikferland-msft mikferland-msft left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great additions overall! My only suggestion is to avoid referring to "managed personal productivity". The rest looks great!

@MicrosoftDocs MicrosoftDocs deleted a comment from mikferland-msft May 23, 2024
Copy link

Learn Build status updates of commit e04c450:

✅ Validation status: passed

File Status Preview URL Details
power-platform/admin/environment-groups.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@tapanm-MSFT tapanm-MSFT merged commit 1d51e4b into MicrosoftDocs:main May 23, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants