Skip to content

Commit 59c0c75

Browse files
committed
tooling add
1 parent f0c2369 commit 59c0c75

1 file changed

Lines changed: 10 additions & 0 deletions

File tree

articles/sentinel/sap/deploy-data-connector-agent-container.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -374,6 +374,16 @@ At this stage, the system's **Health** status is **Pending**. If the agent is up
374374
> [!IMPORTANT]
375375
> There may be some wait time on initial connect. Find more details to verify the connector [here](/azure/sentinel/create-codeless-connector#verify-the-codeless-connector).
376376
377+
## Mass-Onboard SAP systems at scale
378+
379+
To onboard SAP systems to the Sentinel Solution for SAP applications at scale, API and CLI based approaches are recommended. Get started with [this script library](https://github.com/Azure/Azure-Sentinel/tree/master/Solutions/SAP/Tools/IntegrationSuite).
380+
381+
## Rotate the BTP client secret
382+
383+
We recommend that you periodically rotate the BTP subaccount client secrets used by the data connector. For an automated, platform-based approach, see our [Automatic SAP BTP trust store certificate renewal with Azure Key Vault – or how to stop thinking about expiry dates once and for all](https://community.sap.com/t5/technology-blogs-by-members/automatic-sap-btp-trust-store-certificate-renewal-with-azure-key-vault-or/ba-p/13565138) (SAP blog).
384+
385+
This [script library](https://github.com/Azure/Azure-Sentinel/tree/master/Solutions/SAP/Tools/IntegrationSuite) demonstrates the automatic process of updating an existing data connector with a new secret.
386+
377387
## Customize data connector behavior (optional)
378388
379389
If you have an SAP agentless data connector for Microsoft Sentinel, you can use the SAP Integration Suite to customize how the agentless data connector ingests data from your SAP system into Microsoft Sentinel.

0 commit comments

Comments
 (0)