Skip to content

Purview urls updated to new portal and new Purview category#192

Open
Shellgio wants to merge 2 commits intomerill:mainfrom
Shellgio:purview161
Open

Purview urls updated to new portal and new Purview category#192
Shellgio wants to merge 2 commits intomerill:mainfrom
Shellgio:purview161

Conversation

@Shellgio
Copy link
Contributor

This PR changes old compliance portal URLs (compliance.microsoft.com) to the new portal (purview.microsoft.com).
All Purview links where changed category from "Microsoft 365" to "Purview" to address #161

Old urls (compliance.microsoft.com) updated to the new portal (purview.microsoft.com
Changed category from "Microsoft 365" to "Purview" to address merill#161
Updated https://purview.microsoft.com/priva/prm to change category from Microsoft 365 to Purview to address merill#161
@gemini-code-assist
Copy link

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request standardizes the configuration of Microsoft Purview links by updating their URLs to reflect the new Purview portal domain and reclassifying their category from 'Microsoft 365' to 'Purview'. These changes ensure consistency and accuracy in how Purview services are referenced and categorized.

Highlights

  • URL Updates: Updated all Purview-related URLs from the old compliance portal (compliance.microsoft.com) to the new Purview portal (purview.microsoft.com or purview.microsoft.us).
  • Category Refinement: Changed the category for all Purview links within the commands.csv file from 'Microsoft 365' to the more specific 'Purview'.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request successfully updates the Purview-related URLs from the old compliance portal to the new purview portal and correctly changes their category from 'Microsoft 365' to 'Purview'. The changes are generally correct and align with the PR's goal. I've found one potential issue with a URL for a GCC High environment that appears to point to a commercial endpoint, which I've detailed in a specific comment.

pucmgrg,decmg,Purview Compliance manager for GCC High,Microsoft Compliance Manager,Purview,https://purview.microsoft.us/compliancemanager
pucloudgov,,Purview App Governance,,Purview,https://purview.microsoft.com/cloudapps/app-governance
puaudit,,Purview Audit,Microsoft 365 Advanced Audit,Purview,https://purview.microsoft.com/audit/auditsearch
puauditg,,Purview Audit for GCC High,Microsoft 365 Advanced Audit,Purview,https://purview.microsoft.com/auditlogsearch

Choose a reason for hiding this comment

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

high

The URL for 'Purview Audit for GCC High' appears to be pointing to the commercial endpoint (purview.microsoft.com) instead of the GCC High endpoint. For consistency with other GCC High services in this file, it should likely use the .us top-level domain.

puauditg,,Purview Audit for GCC High,Microsoft 365 Advanced Audit,Purview,https://purview.microsoft.us/auditlogsearch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant