Skip to content

Commit 17f5f8b

Browse files
authored
Merge pull request #265986 from austinmccollum/austinmc-restore-apilinks
replace removed links from PR264103
2 parents 8b51b3f + fd6f7db commit 17f5f8b

File tree

5 files changed

+12
-14
lines changed

5 files changed

+12
-14
lines changed

articles/sentinel/create-codeless-connector-legacy.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -584,7 +584,7 @@ After creating your [JSON configuration file](#create-a-connector-json-configura
584584

585585
# [Connect via API](#tab/connect-via-api)
586586

587-
Use the CONNECT endpoint to send a PUT method and pass the JSON configuration directly in the body of the message. For more information, see [auth configuration](#auth-configuration).
587+
Use the [CONNECT](/rest/api/securityinsights/data-connectors/connect) endpoint to send a PUT method and pass the JSON configuration directly in the body of the message. For more information, see [auth configuration](#auth-configuration).
588588

589589
Use the following API attributes, depending on the [authType](#authtype) defined. For each `authType` parameter, all listed attributes are mandatory and are string values.
590590

articles/sentinel/create-codeless-connector.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -103,7 +103,7 @@ To understand how to create a complex DCR with multiple data flows, see the [DCR
103103

104104
This component renders the UI for the data connector in the Microsoft Sentinel data connector gallery. Each data connector may have only one UI definition.
105105

106-
Build the data connector user interface with the **Data Connector Definition** API. Use the [Data connector definitions reference](data-connector-ui-definitions-reference.md) as a supplement to explain the API elements in greater detail.
106+
Build the data connector user interface with the [**Data Connector Definition** API](/rest/api/securityinsights/data-connector-definitions). Use the [Data connector definitions reference](data-connector-ui-definitions-reference.md) as a supplement to explain the API elements in greater detail.
107107

108108
Notes:
109109
1) The `kind` property for API polling connector should always be `Customizable`.

articles/sentinel/data-connector-ui-definitions-reference.md

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -12,15 +12,15 @@ ms.author: austinmc
1212

1313
# Data connector definitions reference for the Codeless Connector Platform
1414

15-
To create a data connector with the Codeless Connector Platform (CCP), use this document as a supplement to the Microsoft Sentinel REST API for Data Connector Definitions reference docs. Specifically this reference document expands on the following section:
15+
To create a data connector with the Codeless Connector Platform (CCP), use this document as a supplement to the [Microsoft Sentinel REST API for Data Connector Definitions](/rest/api/securityinsights/data-connector-definitions) reference docs. Specifically this reference document expands on the following section:
1616

1717
- `connectorUiConfig` - defines the visual elements and text displayed on the data connector page in Microsoft Sentinel.
1818

1919
For more information, see [Create a codeless connector](create-codeless-connector.md).
2020

2121
## Data connector definitions - Create or update
2222

23-
Reference the Create Or Update operation in the REST API docs to find the latest stable or preview API version. The difference between the `create` and the `update` operation is the update requires the `etag` value.
23+
Reference the Create Or Update operation in the REST API docs to find the latest stable or preview API version. Only the `update` operation requires the `etag` value.
2424

2525
**PUT** method
2626
```http
@@ -29,8 +29,6 @@ https://management.azure.com/subscriptions/{{subscriptionId}}/resourceGroups/{{r
2929

3030
## URI parameters
3131

32-
For more information, see [Data Connector Definitions - Create or Update URI Parameters](/rest/api/securityinsights/data-connectors/create-or-update#uri-parameters)
33-
3432
|Name | Description |
3533
|---------|---------|
3634
| **dataConnectorDefinition** | The data connector definition must be a unique name and is the same as the `name` parameter in the [request body](#request-body).|
@@ -335,7 +333,7 @@ Some **InstallAgent** types appear as a button, others appear as a link. Here ar
335333

336334
## Example data connector definition
337335

338-
The following example brings together some of the components defined in this article as a JSON body format to use with the Create Or Update data connector API.
336+
The following example brings together some of the components defined in this article as a JSON body format to use with the Create Or Update data connector definition API.
339337

340338
For more examples of the `connectorUiConfig` review [other CCP data connectors](https://github.com/Azure/Azure-Sentinel/tree/master/DataConnectors#codeless-connector-platform-ccp-preview--native-microsoft-sentinel-polling). Even connectors using the legacy CCP have valid examples of the UI creation.
341339

articles/sentinel/threat-intelligence-integration.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -149,12 +149,12 @@ For more information about how to find and manage the solutions, see [Discover a
149149
### Recorded Future Security Intelligence Platform
150150

151151
- Find and enable incident enrichment playbooks for [Recorded Future](https://www.recordedfuture.com/integrations/microsoft-azure/) in the [Microsoft Sentinel GitHub repository](https://github.com/Azure/Azure-Sentinel/tree/master/Playbooks). Search for subfolders beginning with "RecordedFuture_".
152-
- See the Recorded Future Logic App [connector documentation](/connectors/recordedfuture/).
152+
- See the Recorded Future Logic App [connector documentation](/connectors/recordedfuturev2/).
153153

154154
### ReversingLabs TitaniumCloud
155155

156156
- Find and enable incident enrichment playbooks for [ReversingLabs](https://www.reversinglabs.com/products/file-reputation-service) in the [Microsoft Sentinel GitHub repository](https://github.com/Azure/Azure-Sentinel/tree/master/Solutions/ReversingLabs/Playbooks/ReversingLabs-EnrichFileHash).
157-
- See the ReversingLabs Intelligence Logic App connector documentation.
157+
- See the ReversingLabs TitaniumCloud Logic App [connector documentation](/connectors/reversinglabstitaniu/).
158158

159159
### RiskIQ Passive Total
160160

articles/sentinel/workspace-manager.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -122,11 +122,11 @@ Common reasons for failure include:
122122
- Currently, deleting content residing in member workspace(s) centrally via workspace manager isn't supported.
123123

124124
### API references
125-
- Workspace Manager Assignment Jobs
126-
- Workspace Manager Assignments
127-
- *Workspace Manager Configurations*
128-
- Workspace Manager Groups
129-
- Workspace Manager Members
125+
- [Workspace Manager Assignment Jobs](/rest/api/securityinsights/workspace-manager-assignment-jobs)
126+
- [Workspace Manager Assignments](/rest/api/securityinsights/workspace-manager-assignments)
127+
- [Workspace Manager Configurations](/rest/api/securityinsights/workspace-manager-configurations)
128+
- [Workspace Manager Groups](/rest/api/securityinsights/workspace-manager-groups)
129+
- [Workspace Manager Members](/rest/api/securityinsights/workspace-manager-members)
130130

131131
## Next steps
132132
- [Manage multiple tenants in Microsoft Sentinel as an MSSP](multiple-tenants-service-providers.md)

0 commit comments

Comments
 (0)