Skip to content

Commit 5c20df2

Browse files
committed
bring back mass onboard section
1 parent 2efd98c commit 5c20df2

1 file changed

Lines changed: 4 additions & 0 deletions

File tree

articles/sentinel/sap/deploy-sap-btp-solution.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -109,6 +109,10 @@ You also can retrieve the logs via the UI:
109109
1. In the new instance, create a service key.
110110
1. View the service key and retrieve the required parameters from step 4 of the configuration instructions in the data connector UI (**url**, **uaa.url**, **uaa.clientid**, and **uaa.clientsecret**).
111111

112+
## Mass-Onboard SAP BTP subaccounts at scale
113+
114+
To onboard SAP BTP subaccounts at scale, API and CLI based approaches are recommended. Get started with [this script library](https://github.com/Azure/Azure-Sentinel/blob/master/Solutions/SAP%20BTP/Tools/).
115+
112116
## Rotate the BTP client secret
113117

114118
We recommend that you periodically rotate the BTP subaccount client secrets. 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).

0 commit comments

Comments
 (0)