Skip to content

changed the value of tier property to Partner for bitsight ccf connector#14397

Merged
destinywu merged 2 commits into
Azure:masterfrom
RodrigoLopezCam:users/v-rodrigolop/bitsight
Jun 3, 2026
Merged

changed the value of tier property to Partner for bitsight ccf connector#14397
destinywu merged 2 commits into
Azure:masterfrom
RodrigoLopezCam:users/v-rodrigolop/bitsight

Conversation

@RodrigoLopezCam
Copy link
Copy Markdown
Contributor

@RodrigoLopezCam RodrigoLopezCam commented Jun 2, 2026

Change(s):

BitSight Security Statistics (BitSight_CCF/ConnectorDefinition.json) — ingests Company Profiles, Company Rating Details, Diligence Historical Statistics, Risk Vector Statistics, Industries Statistics, Findings Summary, and Vulnerability reference data into 7 custom tables: BitSightCompanyDetails_CL, BitSightCompanyRatingDetails_CL, BitSightDiligenceHistoricalStatistics_CL, BitSightDiligenceStatistics_CL, BitsightIndustrialStatistics_CL, BitSightFindingsSummary_CL, BitsightVulnerabilitiesFindingsSummary_CL.

BitSight Security Events (BitSight_Events_CCF/ConnectorDefinition.json) — ingests Alerts, Breaches, and security Findings (Diligence, Compromised Systems, User Behavior) into 3 custom tables: BitSightAlerts_CL, BitSightBreaches_CL, BitSightFindings_CL.

Reason for Change(s):

Was updated the value of tier to Partner

Version Updated:

3.2.0

Testing Completed:

Yes. Both CCF connectors were deployed via custom ARM template deployment to a test Microsoft Sentinel workspace. The BitSightStatisticsConnector successfully created all 7 tables and the DCR. The BitSightEventsConnector successfully created all 3 tables and the DCR. A fix was applied to mainTemplate.json to ensure BitSightAlerts_CL and BitSightBreaches_CL table definitions are included in the Events connector's contentTemplates block (packaging tool limitation with multiple CCP connectors in the same solution).
Checked that the validations are passing and have addressed any issues that are present:

All 3 package JSON files (mainTemplate.json, createUiDefinition.json, testParameters.json) pass JSON validation. The createSolutionV3.ps1 ARM-TTK run passes 48/49 checks — the single failing check (Package) is a pre-existing failure unrelated to these changes and present in prior versions of this solution. Both CCF connector ConnectorDefinition.json IDs match their respective connectorDefinitionName values in the polling configs.

BitEv001 BitStat00

@RodrigoLopezCam RodrigoLopezCam requested review from a team as code owners June 2, 2026 22:53
destinywu
destinywu previously approved these changes Jun 2, 2026
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Updates BitSight solution metadata to reflect Partner support tier and propagates that change into the packaged ARM template content.

Changes:

  • Changed support.tier from Microsoft to Partner in solution metadata.
  • Updated packaged mainTemplate.json to reflect Partner tier (and includes additional formatting/ordering diffs).

Reviewed changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated 3 comments.

File Description
Solutions/BitSight/SolutionMetadata.json Updates solution metadata support tier to Partner.
Solutions/BitSight/Package/mainTemplate.json Updates packaged content to match Partner tier (plus additional generated/formatting changes).

Comment thread Solutions/BitSight/SolutionMetadata.json
Comment thread Solutions/BitSight/Package/mainTemplate.json
Comment thread Solutions/BitSight/SolutionMetadata.json
Comment thread Solutions/BitSight/Package/4.0.0.zip Outdated
@destinywu destinywu merged commit 245c832 into Azure:master Jun 3, 2026
33 of 34 checks passed
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.

5 participants