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

Replaced compliance portal URLs with purview portal alternatives #155

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

mpowelltech
Copy link
Contributor

Now that compliance portal is retired, I switched as many URLs as I could from Compliance to the new Purview alternatives.

Couple notes to be aware of:

  1. Not sure if this same retirement applies to GCC High and I can't test this, so I didn't touch those.
  2. pucloudgov - Could not find where this lives now - my guess is it's now part of Defender for Cloud Apps, but that has no real "Cloud App Governance" section I could find, so I left this as-is also.
  3. puclassifiers - There is no real top-level Data Classification page in the new portal, only the sub-pages for SIT, Trainable Classifiers, and EDM, so I pointed this one to the SIT sub-page. This makes it a duplicate of pusit, so not sure if it's better suited as just being an alias of that, but have kept these separate for now.
  4. Speaking of puclassifiers and pusit, these also appear to exist under the Records management solution (https://purview.microsoft.com/recordsmanagement/dataclassification/multicloudsensitiveinfotypes) as well as the Communication Compliance solution. My guess is you can make changes in either and they point to the same place under the hood, but for now I've pointed it to the URL of the CC version.
  5. pucontentse and puedisc - I have left these pointing to the Classic eDiscovery pages in the Purview portal rather than the newest ones as the newest ones are still in preview.

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