Updated to fix class name, add PolicySource parameter

[mtniehaus]

Based on what I ran into implementing an alternate content provider.

[mtniehaus]

@microsoft-github-policy-service agree [company="Tanium"]

[mtniehaus]

@microsoft-github-policy-service agree company="Tanium"

[prmerger-automator]

@mtniehaus : Thanks for your contribution! The author(s) have been notified to review your proposed change.

[prmerger-automator]

@mtniehaus : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

[MandiOhlinger]

@mtniehaus Hi - This PR has a merge conflict. If it's still needed, can you create a new pull request? We want to make sure you get credit for the doc change.

[learn-build-service-prod]

Learn Build status updates of commit ce151dd:

❌ Validation status: errors

Please follow instructions here which may help to resolve issue.

File	Status	Preview URL	Details
	❌Error		Details

• [Error: CannotMergeCommit] Cannot merge commit ce151dd15a1e0b4af52fdb3de62bac30799c4faa in branch patch-2 of repository https://github.com/mtniehaus/memdocs into branch main (commit ee604af789c6659f7162ec066d3b91c8b0686863). Please follow this documentation: https://help.github.com/articles/resolving-a-merge-conflict-using-the-command-line/ to use git.exe to resolve you content conflicts locally and then push to remote.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

[Yupiter2005]

Hello @mtniehaus! It's my honor to review this PR.

Unfortunately, it stayed in limbo long enough - and the source git branch became stale. Could you follow the guidance on merging the conflict above? Alternatively, you can just resubmit the PR from the fresh branch - and I'll approve it.

Thanks in advance!