changed the value of tier property to Partner for bitsight ccf connector#14397
Merged
destinywu merged 2 commits intoJun 3, 2026
Merged
Conversation
destinywu
previously approved these changes
Jun 2, 2026
Contributor
There was a problem hiding this comment.
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.tierfromMicrosofttoPartnerin solution metadata. - Updated packaged
mainTemplate.jsonto 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). |
jlheard
requested changes
Jun 3, 2026
destinywu
approved these changes
Jun 3, 2026
jlheard
approved these changes
Jun 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.