Merge pull request #300653 from EdB-MSFT/CCP-CCF-rebrand

CCP-> CCF

Author: ttorble

articles/sentinel/TOC.yml

@@ -721,7 +721,7 @@
     href: sentinel-solution-quality-guidance.md
   - name: Partner integrations best practices
     href: partner-integrations.md
-  - name: Creating codeless data connectors (CCP)
+  - name: Creating codeless data connectors (CCF)
     href: create-codeless-connector.md
   - name: Creating analytics rules
     href: sentinel-analytic-rules-creation.md

articles/sentinel/connect-data-sources.md

@@ -54,7 +54,7 @@ To add more data connectors, install the solution associated with the data conne
 
 If you're unable to connect your data source to Microsoft Sentinel using any of the existing solutions available, consider creating your own data source connector. For example, many security solutions provide a set of APIs for retrieving log files and other security data from their product or service. Those APIs connect to Microsoft Sentinel with one of the following methods:
 
-- The data source APIs are configured with the [Codeless Connector Platform](create-codeless-connector.md).
+- The data source APIs are configured with the [Codeless Connector Framework](create-codeless-connector.md).
 - The data connector uses the Log Ingestion API for Azure Monitor as part of an [Azure Function](connect-azure-functions-template.md) or [Logic App](create-custom-connector.md#connect-with-logic-apps).
 
 You can also use Azure Monitor Agent directly or Logstash to create your custom connector. For more information, see [Resources for creating Microsoft Sentinel custom connectors](create-custom-connector.md).

articles/sentinel/connect-google-cloud-platform.md

@@ -16,7 +16,7 @@ Organizations are increasingly moving to multicloud architectures, whether by de
 
 This article describes how to ingest GCP data into Microsoft Sentinel to get full security coverage and analyze and detect attacks in your multicloud environment.
 
-With the **GCP Pub/Sub** connectors, based on our [Codeless Connector Platform (CCP)](create-codeless-connector.md?tabs=deploy-via-arm-template%2Cconnect-via-the-azure-portal), you can ingest logs from your GCP environment using the GCP [Pub/Sub capability](https://cloud.google.com/pubsub/docs/overview):
+With the **GCP Pub/Sub** connectors, based on our [Codeless Connector Framework (CCF)](create-codeless-connector.md?tabs=deploy-via-arm-template%2Cconnect-via-the-azure-portal), you can ingest logs from your GCP environment using the GCP [Pub/Sub capability](https://cloud.google.com/pubsub/docs/overview):
 
 - The **Google Cloud Platform (GCP) Pub/Sub Audit Logs connector** collects audit trails of access to GCP resources. Analysts can monitor these logs to track resource access attempts and detect potential threats across the GCP environment.
 

articles/sentinel/create-codeless-connector.md

@@ -1,6 +1,6 @@
 ---
 title: Create a codeless connector for Microsoft Sentinel
-description: Learn how to create a codeless connector in Microsoft Sentinel using the Codeless Connector Platform (CCP).
+description: Learn how to create a codeless connector in Microsoft Sentinel using the Codeless Connector Framework (CCF).
 author: austinmccollum
 ms.author: austinmc
 ms.topic: how-to
@@ -12,11 +12,11 @@ ms.date: 09/26/2024
 ---
 # Create a codeless connector for Microsoft Sentinel
 
-The Codeless Connector Platform (CCP) provides partners, advanced users, and developers the ability to create custom connectors for ingesting data to Microsoft Sentinel.
+The Codeless Connector Framework (CCF) provides partners, advanced users, and developers the ability to create custom connectors for ingesting data to Microsoft Sentinel.
 
-Connectors created using the CCP are fully SaaS, with no requirements for service installations. They also include [health monitoring](monitor-data-connector-health.md) and full support from Microsoft Sentinel.
+Connectors created using the CCF are fully SaaS, with no requirements for service installations. They also include [health monitoring](monitor-data-connector-health.md) and full support from Microsoft Sentinel.
 
-**Use the following steps to create your CCP connector and connect your data source to Microsoft Sentinel**
+**Use the following steps to create your CCF connector and connect your data source to Microsoft Sentinel**
 
 > [!div class="checklist"]
 > * Build the data connector
@@ -26,9 +26,9 @@ Connectors created using the CCP are fully SaaS, with no requirements for servic
 
 This article will show you how to complete each step and provide an [example codeless connector](#example) to build along the way.
 
-## How is this CCP different from the previous version?
+## How is this CCF different from the previous version?
 
-The initial version of the CCP was [announced](https://techcommunity.microsoft.com/t5/microsoft-sentinel-blog/the-codeless-connector-platform/ba-p/3095455) in January of 2022. Since then, we've improved upon the platform and the [legacy release](create-codeless-connector-legacy.md) is no longer recommended. This new version of the CCP has the following key improvements:
+The initial version of the CCF was [announced](https://techcommunity.microsoft.com/t5/microsoft-sentinel-blog/the-codeless-connector-platform/ba-p/3095455) in January of 2022. Since then, we've improved upon the platform and the [legacy release](create-codeless-connector-legacy.md) is no longer recommended. This new version of the CCF has the following key improvements:
 
 1. Better support for various authentication and pagination types.
 
@@ -75,7 +75,7 @@ We recommend testing your components with an API testing tool like one of the fo
 
 ## Build the data connector
 
-There are four components required to build the CCP data connector.
+There are four components required to build the CCF data connector.
 
 1. [Output table definition](#output-table-definition)
 1. [Data Collection Rule (DCR)](#data-collection-rule)
@@ -104,7 +104,7 @@ Data collection rules (DCRs) define the data collection process in Azure Monitor
 
 - There is only one DCR that gets deployed per data connector.
 - A DCR must have a corresponding DCE in the same region.
-- When the CCP data connector is deployed, the DCR is created if it doesn't already exist.
+- When the CCF data connector is deployed, the DCR is created if it doesn't already exist.
 
 Reference the latest information on DCRs in these articles:
 - [Data collection rules overview](/azure/azure-monitor/essentials/data-collection-rule-overview)
@@ -131,7 +131,7 @@ To learn from an example, see the [Data connector definitions reference example
 
 ### Data connection rules
 
-There are currently two kinds of data connection rules possible for defining your CCP data connector.
+There are currently two kinds of data connection rules possible for defining your CCF data connector.
 
 - `RestApiPoller` kind allows you to customize paging, authorization and expected request/response payloads for your data source. For more information, see [RestApiPoller data connector connection rules reference](data-connector-connection-rules-reference.md).
 - `GCP` kind allows you to decrease your development time by automatically configuring paging and expected response payloads for your Google Cloud Platform (GCP) data source. For more information, see [GCP data connector connection rules reference](data-connection-rules-reference-gcp.md)
@@ -140,7 +140,7 @@ Use an [API testing tool](#testing-apis) to call the data connector API to creat
 
 ## Secure confidential input
 
-Whatever authentication is used by your CCP data connector, take these steps to ensure confidential information is kept secure. The goal is to pass along credentials from the ARM template to the CCP without leaving readable confidential objects in your deployments history.
+Whatever authentication is used by your CCF data connector, take these steps to ensure confidential information is kept secure. The goal is to pass along credentials from the ARM template to the CCF without leaving readable confidential objects in your deployments history.
 
 ### Create label
 
@@ -218,19 +218,19 @@ Finally, the CCP utilizes the credential objects in the data connector section.
 
 Manually package an Azure Resource Management (ARM) template using the [example template code samples](#example-arm-template) as your guide. These code samples are divided by ARM template sections which you must splice together.
 
-If you're creating a Google Cloud Platform (GCP) CCP data connector, package the deployment template using the [example GCP CCP template](https://github.com/Azure/Azure-Sentinel/blob/master/DataConnectors/Templates/Connector_GCP_CCP_template.json). For information on how to fill out the GCP CCP template, see [GCP data connector connection rules reference](data-connection-rules-reference-gcp.md).
+If you're creating a Google Cloud Platform (GCP) CCF data connector, package the deployment template using the [example GCP CCF template](https://github.com/Azure/Azure-Sentinel/blob/master/DataConnectors/Templates/Connector_GCP_CCP_template.json). For information on how to fill out the GCP CCF template, see [GCP data connector connection rules reference](data-connection-rules-reference-gcp.md).
 
-In addition to the example templates, published solutions available in the Microsoft Sentinel content hub use the CCP for their data connectors. Review the following solutions as more examples of how to stitch the components together into an ARM template.
+In addition to the example templates, published solutions available in the Microsoft Sentinel content hub use the CCF for their data connectors. Review the following solutions as more examples of how to stitch the components together into an ARM template.
 
-**`RestApiPoller`** CCP data connector examples
+**`RestApiPoller`** CCF data connector examples
 - [Ermes Browser Security](https://github.com/Azure/Azure-Sentinel/tree/master/Solutions/Ermes%20Browser%20Security/Data%20Connectors/ErmesBrowserSecurityEvents_ccp)
 - [Palo Alto Prisma Cloud CWPP](https://github.com/Azure/Azure-Sentinel/tree/master/Solutions/Palo%20Alto%20Prisma%20Cloud%20CWPP/Data%20Connectors/PaloAltoPrismaCloudCWPP_ccp)
 - [Sophos Endpoint Protection](https://github.com/Azure/Azure-Sentinel/tree/master/Solutions/Sophos%20Endpoint%20Protection/Data%20Connectors/SophosEP_ccp)
 - [Workday](https://github.com/Azure/Azure-Sentinel/tree/master/Solutions/Workday/Data%20Connectors/Workday_ccp)
 - [Atlassian Jira](https://github.com/Azure/Azure-Sentinel/tree/master/Solutions/AtlassianJiraAudit/Data%20Connectors/JiraAuditAPISentinelConnector_ccpv2)
 - [Okta Single Sign-On](https://github.com/Azure/Azure-Sentinel/tree/master/Solutions/Okta%20Single%20Sign-On/Data%20Connectors/OktaNativePollerConnectorV2)
 
-**`GCP`** CCP data connector examples
+**`GCP`** CCF data connector examples
 - [GCP audit logs](https://github.com/Azure/Azure-Sentinel/blob/master/Solutions/Google%20Cloud%20Platform%20Audit%20Logs/Package/mainTemplate.json)
 - [GCP security command center](https://github.com/Azure/Azure-Sentinel/blob/master/Solutions/Google%20Cloud%20Platform%20Security%20Command%20Center/Package/mainTemplate.json)
 
@@ -246,9 +246,9 @@ Deploy your codeless connector as a custom template.
 
 ### Maintain network isolation for logging source
 
-If your logging source requires network isolation, configure an allowlist of public IP addresses used by the CCP.
+If your logging source requires network isolation, configure an allowlist of public IP addresses used by the CCF.
 
-Azure virtual networks use service tags to define network access controls. For the CCP, that service tag is [**Scuba**](/azure/virtual-network/service-tags-overview#available-service-tags).
+Azure virtual networks use service tags to define network access controls. For the CCF, that service tag is [**Scuba**](/azure/virtual-network/service-tags-overview#available-service-tags).
 
 To find the current IP range associated with the **Scuba** service tag, see [Use the Service Tag Discovery API](/azure/virtual-network/service-tags-overview#use-the-service-tag-discovery-api).
 
@@ -268,10 +268,10 @@ Each step in building the codeless connector is represented in the following exa
 - [Example custom table](#example-custom-table)
 - [Example data collection rule](#example-data-collection-rule)
 - [Example data connector UI definition](data-connector-ui-definitions-reference.md#example-data-connector-definition)
-- [Example data connection rules](data-connector-connection-rules-reference.md#example-ccp-data-connector)
+- [Example data connection rules](data-connector-connection-rules-reference.md#example-ccf-data-connector)
 - [Use example data with example template](#example-arm-template)
 
-To demonstrate a complex data source with ingestion to more than one table, this example features an output table schema and a DCR with multiple output streams. The DCR example puts these together along with its KQL transforms. The data connector UI definition and connection rules examples continue from this same example data source. Finally, the solution template uses all these example components to show end to end how to create the example CCP data connector.
+To demonstrate a complex data source with ingestion to more than one table, this example features an output table schema and a DCR with multiple output streams. The DCR example puts these together along with its KQL transforms. The data connector UI definition and connection rules examples continue from this same example data source. Finally, the solution template uses all these example components to show end to end how to create the example CCF data connector.
 
 ### Example data
 
@@ -451,11 +451,11 @@ This example is located in the [Data connector definitions reference](data-conne
 
 ### Example data connector connection rules
 
-This example is located in the [Data connectors reference](data-connector-connection-rules-reference.md#example-ccp-data-connector).
+This example is located in the [Data connectors reference](data-connector-connection-rules-reference.md#example-ccf-data-connector).
 
 ### Example ARM template
 
-Build the ARM deployment template with the following structure, which includes the 4 sections of JSON components required to build the CCP data connector:
+Build the ARM deployment template with the following structure, which includes the 4 sections of JSON components required to build the CCF data connector:
 
 ```json
 {
@@ -554,7 +554,7 @@ These recommended variables help simplify the template. Use more or less as need
 ```
 #### Example ARM template - resources
 
-There are 5 ARM deployment resources in this template guide which house the 4 CCP data connector building components. 
+There are 5 ARM deployment resources in this template guide which house the 4 CCF data connector building components. 
 
 1. **contentTemplates** (a parent resource)
     - metadata

articles/sentinel/create-custom-connector.md

@@ -23,7 +23,7 @@ The following table compares essential details about each method for creating cu
 
 |Method description  |Capability | Serverless    |Complexity  |
 |---------|---------|---------|---------|
-| **[Codeless Connector Platform (CCP)](#connect-with-the-codeless-connector-platform)** <br>Best for less technical audiences to create SaaS connectors using a configuration file instead of advanced development. | Supports all capabilities available with the code. | Yes | Low; simple, codeless development
+| **[Codeless Connector Framework (CCF)](#connect-with-the-codeless-connector-framework)** <br>Best for less technical audiences to create SaaS connectors using a configuration file instead of advanced development. | Supports all capabilities available with the code. | Yes | Low; simple, codeless development
 |**[Azure Monitor Agent](#connect-with-the-azure-monitor-agent)** <br>Best for collecting files from on-premises and IaaS sources   | File collection, data transformation  |   No      | Low         |
 |**[Logstash](#connect-with-logstash)** <br>Best for on-premises and IaaS sources, any source for which a plugin is available, and organizations already familiar with Logstash  | Supports all capabilities of the Azure Monitor Agent  |   No; requires a VM or VM cluster to run           |   Low; supports many scenarios with plugins      |
 |**[Logic Apps](#connect-with-logic-apps)** <br>High cost; avoid for high-volume data <br>Best for low-volume cloud sources  | Codeless programming allows for limited flexibility, without support for implementing algorithms.<br><br> If no available action already supports your requirements, creating a custom action may add complexity.    |    Yes         |   Low; simple, codeless development      |
@@ -38,11 +38,11 @@ The following table compares essential details about each method for creating cu
 > - Office 365 (Microsoft Sentinel GitHub community): [Logic App connector](https://github.com/Azure/Azure-Sentinel/tree/master/Playbooks/Get-O365Data) | [Azure Function connector](https://github.com/Azure/Azure-Sentinel/tree/master/DataConnectors/O365%20Data)
 >
 
-## Connect with the Codeless Connector Platform
+## Connect with the Codeless Connector Framework
 
-The Codeless Connector Platform (CCP) provides a configuration file that can be used by both customers and partners, and then deployed to your own workspace, or as a solution to Microsoft Sentinel's content hub.
+The Codeless Connector Framework (CCF) provides a configuration file that can be used by both customers and partners, and then deployed to your own workspace, or as a solution to Microsoft Sentinel's content hub.
 
-Connectors created using the CCP are fully SaaS, without any requirements for service installations, and also include health monitoring and full support from Microsoft Sentinel.
+Connectors created using the CCF are fully SaaS, without any requirements for service installations, and also include health monitoring and full support from Microsoft Sentinel.
 
 For more information, see [Create a codeless connector for Microsoft Sentinel](create-codeless-connector.md).