Skip to content

Privacy opt-in for Semantic Data Search#6919

Open
SVinchi wants to merge 6 commits intomainfrom
private/shvinc/copilotaipage
Open

Privacy opt-in for Semantic Data Search#6919
SVinchi wants to merge 6 commits intomainfrom
private/shvinc/copilotaipage

Conversation

@SVinchi
Copy link

@SVinchi SVinchi commented Mar 2, 2026

  • Adding a group on Copilot and AI settings page to define privacy notice for Semantic Data Search
  • Register Semantic Data Search privacy notice in SystemPrivacyNoticeReg
  • Add UI toggle and privacy notice integration on Copilot AI Capabilities page

Porting changes from Platform-Core PR #233155

Fixes AB#623789

@SVinchi SVinchi requested review from a team as code owners March 2, 2026 13:53
@github-actions github-actions bot added this to the Version 29.0 milestone Mar 2, 2026
encimita
encimita previously approved these changes Mar 2, 2026
…s.Page.al

Co-authored-by: Darrick <darjoo@users.noreply.github.com>
@msft-sam
Copy link
Contributor

msft-sam commented Mar 3, 2026

Does the data apply to across companies? We have some logic where we enable the privacy notice for evaluation companies, but if we build the metadata across all companies this could be an issue, as switching company would then mark the notice as disabled. As this is the object metadata and is across companies, we probably need to leave it disabled, even for eval companies.

edit: alternatively, what is the difference between this and the AOAI privacy notice -- aren't we sending the data to the same place?

@SVinchi
Copy link
Author

SVinchi commented Mar 3, 2026

Does the data apply to across companies? We have some logic where we enable the privacy notice for evaluation companies, but if we build the metadata across all companies this could be an issue, as switching company would then mark the notice as disabled. As this is the object metadata and is across companies, we probably need to leave it disabled, even for eval companies.

When privacy notice is enabled, the approval is stored without any company identifier. This means privacy approval is applied across companies

edit: alternatively, what is the difference between this and the AOAI privacy notice -- aren't we sending the data to the same place?

AOAI privacy notice is conditional and only shown when AOAI services are not present in the region. The privacy notice for semantic search needs to be shown in all regions and hence we could not re-purpose AOAI privacy notice

@msft-sam
Copy link
Contributor

msft-sam commented Mar 3, 2026

When privacy notice is enabled, the approval is stored without any company identifier. This means privacy approval is applied across companies

There is an edge case where the privacy notice is not set. When validated through Copilot capabilities the SkipCheckInEval parameter is set to true. We probably need to include additional metadata to indicate whether we can do this for scenarios such as this one, so the notice is consistently respected in eval and non-eval companies in the event we send data that is not per company.

AOAI privacy notice is conditional and only shown when AOAI services are not present in the region.

I assume you will be able to follow the same logic, consent is only needed if you leave the current geo. Admins can still control the consent via the privacy notices page in any case.

@SVinchi SVinchi enabled auto-merge (squash) March 3, 2026 15:00
@SVinchi
Copy link
Author

SVinchi commented Mar 3, 2026

When privacy notice is enabled, the approval is stored without any company identifier. This means privacy approval is applied across companies

There is an edge case where the privacy notice is not set. When validated through Copilot capabilities the SkipCheckInEval parameter is set to true. We probably need to include additional metadata to indicate whether we can do this for scenarios such as this one, so the notice is consistently respected in eval and non-eval companies in the event we send data that is not per company.

For now we're not using this codeunit to evaluate consent but yes, this needs to be fixed.

@SVinchi SVinchi closed this Mar 3, 2026
auto-merge was automatically disabled March 3, 2026 15:04

Pull request was closed

@SVinchi SVinchi reopened this Mar 3, 2026
@SVinchi SVinchi enabled auto-merge (squash) March 3, 2026 15:11
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