Microsoft/bcquality
1
0
Fork 0
mirror of https://github.com/microsoft/BCQuality.git synced 2026-10-07 15:46:55 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
bcquality/microsoft/knowledge/privacy/register-integration-in-privacy-notice-registrations.md
Jesper Schulz-Wedde 2b5550c346
Some checks failed
Validate knowledge index / validate-index (push) Has been cancelled
Details
Validate AL review fixtures / validate-review-fixtures (push) Has been cancelled
Details
Validate frontmatter and structure / validate (push) Has been cancelled
Details
Improve partner onboarding and documentation navigation (#174) 
Lead with a complete plugin quick start and add task-oriented usage, troubleshooting, customization, and contribution guides. Preserve the broader plugin framing, correct conflicting contract guidance, support Agents folder reviews, and align repository validation. Convert existing sample references to clickable links without changing knowledge rules.

Co-authored-by: Jesper Schulz-Wedde <jesper.schulzwedde@microsoft.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
2026-09-09 17:31:03 +02:00

1.4 KiB
Raw Blame History

bc-version domain keywords technologies countries application-area
all
privacy
privacy-notice
integration
register
onregisterprivacynotices
notice-id
al
w1
all

Register custom integrations with Codeunit Privacy Notice

Description

The current extension point is Codeunit "Privacy Notice". Extensions can subscribe to its OnRegisterPrivacyNotices event and add a dedicated notice ID, integration name, and link to the temporary Privacy Notice record. For explicit creation outside the default-registration flow, the same codeunit exposes CreatePrivacyNotice. Codeunit "Privacy Notice Registrations" contains IDs for built-in integrations and is not the registration API for a custom service.

Best Practice

Choose a stable ID owned by the extension. Register it through OnRegisterPrivacyNotices, or call PrivacyNotice.CreatePrivacyNotice during an intentional setup or upgrade path. Use that same ID for consent checks described in privacy-notice-consent-for-external-data-transfer.md.

See sample: register-integration-in-privacy-notice-registrations.good.al.

Anti Pattern

Reusing the Exchange or another built-in notice ID for a custom integration, subscribing to Privacy Notice Registrations, or calling the nonexistent CreatePrivacyNoticeForIntegration method. These shapes attach consent to the wrong service or do not compile.