Frends iPaaS Audit Logs data connector (via Codeless Connector Framework)#14630
Merged
Conversation
Add README for Frends iPaaS Audit Logs Data Connector with details on deployment, prerequisites, and troubleshooting.
Contributor
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Adds a new Microsoft Sentinel Codeless Connector Framework (CCF) data connector to ingest Frends iPaaS tenant audit trail logs via the Frends Platform API.
Changes:
- Introduces an ARM template that provisions the custom table, DCE/DCR (+ transformKql), solution content package, connector definition UI, and RestApiPoller connection.
- Adds a README documenting prerequisites, deployment, connection steps, and IP allowlisting guidance.
- Adds custom table schema reference files (including KQL validation test asset).
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| DataConnectors/Frends iPaaS/README.md | Documents the connector architecture, prerequisites, deployment/connect flow, and troubleshooting. |
| DataConnectors/Frends iPaaS/FrendsAuditLogs_Sentinel_CCF.json | Main ARM template for table + DCE/DCR + CCF connector definition and connection templates. |
| DataConnectors/Frends iPaaS/FrendsAuditLogs_CL.json | Custom table schema reference for FrendsAuditLogs_CL. |
| .script/tests/KqlvalidationsTests/CustomTables/FrendsAuditLogs_CL.json | Adds the custom table schema to KQL validation test inputs. |
v-shukore
approved these changes
Jul 8, 2026
v-dvedak
approved these changes
Jul 8, 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):
Framework (CCF) data connector.
Trail Log endpoint (GET /api/v1/audit-log) using OAuth 2.0 client
credentials against Microsoft Entra ID (token audience: the Application
ID URI registered with Frends; scope api:///.default).
EventTimestampUtc, Parameters) with DCR ingestion-time transformation
mapping the raw audit entry (actionName, userName, timestamp, parameters)
and guaranteeing a non-null TimeGenerated.
Client ID, Client Secret and Frends tenant name at Connect-time — no
credentials in the deployment template.
PageSize=200 (Frends API maximum).
Reason for Change(s):
trail (configuration changes, user and system actions) is security-
relevant, and no Microsoft Sentinel data connector currently exists
for it.
deployments, permission and configuration changes) alongside other
sources in Microsoft Sentinel, using the fully SaaS CCF — no Function
Apps or Logic Apps to operate.
Version Updated:
(Solution version 1.0.0; data connector definition and connections
versions 1.0.0.)
Testing Completed:
functions or tables. Verified: ARM deployment succeeds (table, DCE, DCR,
connector definition and content templates created), connector page
renders and accepts credentials, OAuth2 client-credentials token
acquisition succeeds, events ingest into FrendsAuditLogs_CL with correct
TimeGenerated mapping, and sample/graph queries return data. No custom
parser or function is required by this solution.
Checked that the validations are passing and have addressed any issues that are present: