Skip to content

Commit 5612feb

Browse files
Merge branch 'ed-app-auth' of https://github.com/microsoftgraph/microsoft-graph-docs into ed-app-auth
2 parents 98ee5f4 + 3f6ca5b commit 5612feb

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

concepts/security-ediscovery-appauthsetup.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ Implement app-only access using Microsoft Graph API to ensure secure and efficie
1818

1919
### Enhancing security and compliance
2020

21-
App-only access enhances the security landscape of Purview eDiscovery by implementing robust authentication protocols that standard user credentials can't match. By using Application (client) IDs and certificates for authentication, we minimize the risk of credential theft, which is a common vulnerability in standard authentication methods. This approach not only secures the application against unauthorized access but also ensures that the data integrity is maintained during the eDiscovery process.
21+
App-only access enhances the security landscape of Purview eDiscovery by implementing robust authentication protocols that standard user credentials can't match. By using application (client) IDs and certificates for authentication, we minimize the risk of credential theft, which is a common vulnerability in standard authentication methods. This approach not only secures the application against unauthorized access but also ensures that the data integrity is maintained during the eDiscovery process.
2222

2323
### Streamlining access and integration
2424

@@ -32,13 +32,13 @@ Implementing app-only access involves registering the app in Azure portal, creat
3232

3333
1. To begin, navigate to the Azure portal and sign in with your Microsoft account.
3434

35-
2. Access the **Microsoft Entra ID** section on the left side.
35+
2. Select **Microsoft Entra ID** on the left side of the Azure portal.
3636

3737
3. Expand **App registrations** on the left side of the Azure portal and select **New registration**.
3838

3939
4. Provide a meaningful name for your application and select register to create your new app registration. This process will generate essential details such as the Application (client) ID and Directory (tenant) ID, which are crucial for future steps.
4040

41-
5. You can now see the newly created app registration and the details.
41+
You can now see the newly created app registration and the details.
4242

4343
![Screenshot of the app registration page.](images/security-ediscovery-appauthsetup-step1.png)
4444

@@ -48,7 +48,7 @@ Now that your app is registered, expand **Manage** on the left of the Azure port
4848

4949
For a client secret, select **New client secret**, add a description, and select **Add** to save it. Make sure to copy and securely store the secret value for authentication later. Otherwise, you may have to create a new secret.
5050

51-
You can optionally upload a certificate to use along with the App ID for automation purposes.
51+
You can optionally upload a certificate to use along with the application ID for automation purposes.
5252

5353
![Screenshot of the app registration client secret page.](images/security-ediscovery-appauthsetup-step2.png)
5454

0 commit comments

Comments
 (0)