Skip to content

Commit 87b5ba5

Browse files
Merge pull request #266222 from msmbaldwin/acl-freshness
Freshness & Acrolinx updates
2 parents fadb2db + c7701e4 commit 87b5ba5

9 files changed

+52
-63
lines changed

articles/confidential-ledger/overview.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -5,13 +5,13 @@ services: confidential-ledger
55
author: msmbaldwin
66
ms.service: confidential-ledger
77
ms.topic: overview
8-
ms.date: 11/14/2022
8+
ms.date: 01/30/2024
99
ms.author: mbaldwin
1010

1111
---
1212
# Microsoft Azure confidential ledger
1313

14-
Microsoft Azure confidential ledger (ACL) is a new and highly secure service for managing sensitive data records. It runs exclusively on hardware-backed secure enclaves, a heavily monitored and isolated runtime environment which keeps potential attacks at bay. Furthermore, Azure confidential ledger runs on a minimalistic Trusted Computing Base (TCB), which ensures that no one⁠—not even Microsoft⁠—is "above" the ledger.
14+
Microsoft Azure confidential ledger (ACL) is a new and highly secure service for managing sensitive data records. It runs exclusively on hardware-backed secure enclaves, a heavily monitored and isolated runtime environment, which keeps potential attacks at bay. Furthermore, Azure confidential ledger runs on a minimalistic Trusted Computing Base (TCB), which ensures that no one⁠—not even Microsoft⁠—is "above" the ledger.
1515

1616
As its name suggests, Azure confidential ledger utilizes the [Azure Confidential Computing platform](../confidential-computing/index.yml) and the [Confidential Consortium Framework](https://ccf.dev) to provide a high integrity solution that is tamper-protected and evident. One ledger spans across three or more identical instances, each of which run in a dedicated, fully attested hardware-backed enclave. The ledger's integrity is maintained through a consensus-based blockchain.
1717

@@ -28,19 +28,19 @@ For more information, you can watch the [Azure confidential ledger demo](https:/
2828

2929
## Key Features
3030

31-
The confidential ledger is exposed through REST APIs which can be integrated into new or existing applications. The confidential ledger can be managed by administrators utilizing Administrative APIs (Control Plane). It can also be called directly by application code through Functional APIs (Data Plane). The Administrative APIs support basic operations such as create, update, get and, delete. The Functional APIs allow direct interaction with your instantiated ledger and include operations such as put and get data.
31+
The confidential ledger is exposed through REST APIs, which can be integrated into new or existing applications. Administrators can manage the confidential ledger with Administrative APIs (Control Plane). The confidential ledger can also be called directly by application code through Functional APIs (Data Plane). The Administrative APIs support basic operations such as create, update, get and, delete. The Functional APIs allow direct interaction with your instantiated ledger and include operations such as put and get data.
3232

3333
## Ledger security
3434

3535
The ledger APIs support certificate-based authentication process with owner roles as well as Microsoft Entra ID based authentication and also role-based access (for example, owner, reader, and contributor).
3636

37-
The data to the ledger is sent through TLS 1.3 connection and the TLS 1.3 connection terminates inside the hardware backed security enclaves (Intel® SGX enclaves). This ensures that no one can intercept the connection between a customer's client and the confidential ledger server nodes.
37+
The data to the ledger is sent through TLS 1.3 connection and the TLS 1.3 connection terminates inside the hardware backed security enclaves (Intel® SGX enclaves), ensuring that no one can intercept the connection between a customer's client and the confidential ledger server nodes.
3838

3939
### Ledger storage
4040

4141
Confidential ledgers are created as blocks in blob storage containers belonging to an Azure Storage account. Transaction data can either be stored encrypted or in plaintext depending on your needs.
4242

43-
The confidential ledger can be managed by administrators utilizing Administrative APIs (Control Plane), and can be called directly by your application code through Functional APIs (Data Plane). The Administrative APIs support basic operations such as create, update, get and, delete.
43+
Administrators can manage the confidential ledger with Administrative APIs (Control Plane), and the confidential ledger can be called directly by your application code through Functional APIs (Data Plane). The Administrative APIs support basic operations such as create, update, get and, delete.
4444

4545
The Functional APIs allow direct interaction with your instantiated confidential ledger and include operations such as put and get data.
4646

@@ -56,8 +56,8 @@ The Functional APIs allow direct interaction with your instantiated confidential
5656
|--|--|
5757
| ACL | Azure confidential ledger |
5858
| Ledger | An immutable append-only record of transactions (also known as a Blockchain) |
59-
| Commit | A confirmation that a transaction has been appended to the ledger. |
60-
| Receipt | Proof that the transaction was processed by the ledger. |
59+
| Commit | A confirmation that a transaction was appended to the ledger. |
60+
| Receipt | Proof that the ledger processed a transaction. |
6161

6262
## Next steps
6363

articles/confidential-ledger/quickstart-cli.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -3,17 +3,17 @@ title: Quickstart – Microsoft Azure confidential ledger with the Azure CLI
33
description: Learn to use the Microsoft Azure confidential ledger through the Azure CLI
44
author: msmbaldwin
55
ms.author: mbaldwin
6-
ms.date: 03/22/2022
6+
ms.date: 01/30/2024
77
ms.service: confidential-ledger
88
ms.custom: devx-track-azurecli
99
ms.topic: quickstart
1010
---
1111

1212
# Quickstart: Create a confidential ledger using the Azure CLI
1313

14-
Azure confidential ledger is a cloud service that provides a high integrity store for sensitive data logs and records that must be kept intact. In this quickstart you will use the [Azure CLI](/cli/azure/) to create a confidential ledger, view and update its properties, and delete it.
14+
Azure confidential ledger is a cloud service that provides a high integrity store for sensitive data logs and records that must be kept intact. In this quickstart, you use the [Azure CLI](/cli/azure/) to create a confidential ledger, view and update its properties, and delete it.
1515

16-
For more information on Azure confidential ledger, and for examples of what can be stored in a confidential ledger, see [About Microsoft Azure confidential ledger](overview.md).
16+
For more information on Azure confidential ledger and examples of what can be stored in a confidential ledger, see [About Microsoft Azure confidential ledger](overview.md).
1717

1818
[!INCLUDE [quickstarts-free-trial-note](../../includes/quickstarts-free-trial-note.md)]
1919

@@ -27,13 +27,13 @@ For more information on Azure confidential ledger, and for examples of what can
2727

2828
## Get your principal ID
2929

30-
To create a confidential ledger, you'll need your Microsoft Entra principal ID (also called your object ID). To obtain your principal ID, use the Azure CLI [az ad signed-in-user](/cli/azure/ad/signed-in-user) command, and filter the results by `objectId`:
30+
To create a confidential ledger, you need your Microsoft Entra principal ID (also called your object ID). To obtain your principal ID, use the Azure CLI [az ad signed-in-user](/cli/azure/ad/signed-in-user) command, and filter the results by `objectId`:
3131

3232
```azurecli
3333
az ad signed-in-user show --query objectId
3434
```
3535

36-
Your result will be in the format `xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx`.
36+
Your result is in the format `xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx`.
3737

3838
## Create a confidential ledger
3939

@@ -43,9 +43,9 @@ Use the Azure CLI [az confidentialledger create](/cli/azure/confidentialledger#a
4343
az confidentialledger create --name "myLedger" --resource-group "myResourceGroup" --location "EastUS" --ledger-type "Public" --aad-based-security-principals ledger-role-name="Administrator" principal-id="<your-principal-id>"
4444
```
4545

46-
A successful operation will return the properties of the newly created ledger. Take note of the **ledgerUri**. In the example above, this URI is "https://myledger.confidential-ledger.azure.com".
46+
A successful operation returns the properties of the newly created ledger. Take note of the **ledgerUri**. In our example, this URI is "https://myledger.confidential-ledger.azure.com".
4747

48-
You'll need this URI to transact with the confidential ledger from the data plane.
48+
You need this URI to transact with the confidential ledger from the data plane.
4949

5050
## View and update your confidential ledger properties
5151

@@ -67,7 +67,7 @@ To update the properties of a confidential ledger, use do so, use the Azure CLI
6767
az confidentialledger update --name "myLedger" --resource-group "myResourceGroup" --ledger-type "Public" --aad-based-security-principals ledger-role-name="Reader" principal-id="<your-principal-id>"
6868
```
6969

70-
If you again run [az confidentialledger show](/cli/azure/confidentialledger#az-confidentialledger-show), you'll see that the role has been updated.
70+
If you again run [az confidentialledger show](/cli/azure/confidentialledger#az-confidentialledger-show), you see that the role is updated.
7171

7272
```json
7373
"ledgerRoleName": "Reader",
@@ -79,6 +79,6 @@ If you again run [az confidentialledger show](/cli/azure/confidentialledger#az-c
7979

8080
## Next steps
8181

82-
In this quickstart, you created a confidential ledger by using the Azure CLI. To learn more about Azure confidential ledger and how to integrate it with your applications, continue on to the articles below.
82+
In this quickstart, you created a confidential ledger by using the Azure CLI. To learn more about Azure confidential ledger and how to integrate it with your applications, continue on to these articles.
8383

8484
- [Overview of Microsoft Azure confidential ledger](overview.md)

articles/confidential-ledger/quickstart-net.md

Lines changed: 5 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Quickstart - Azure confidential ledger client library for .NET
33
description: Learn how to use Azure Confidential Ledger using the client library for .NET
44
author: msmbaldwin
55
ms.author: mbaldwin
6-
ms.date: 07/15/2022
6+
ms.date: 01/30/2024
77
ms.service: confidential-ledger
88
ms.topic: quickstart
99
ms.devlang: csharp
@@ -26,26 +26,22 @@ Azure confidential ledger client library resources:
2626
- [.NET Core 3.1 SDK or later](https://dotnet.microsoft.com/download/dotnet-core)
2727
- [Azure CLI](/cli/azure/install-azure-cli)
2828

29-
You will also need a running confidential ledger, and a registered user with the `Administrator` privileges. You can create a confidential ledger (and an administrator) using the [Azure portal](quickstart-portal.md), the [Azure CLI](quickstart-cli.md), or [Azure PowerShell](quickstart-powershell.md).
29+
You also need a running confidential ledger, and a registered user with the `Administrator` privileges. You can create a confidential ledger (and an administrator) using the [Azure portal](quickstart-portal.md), the [Azure CLI](quickstart-cli.md), or [Azure PowerShell](quickstart-powershell.md).
3030

3131
## Setup
3232

3333
### Create new .NET console app
3434

3535
1. In a command shell, run the following command to create a project named `acl-app`:
36-
3736
```dotnetcli
3837
dotnet new console --name acl-app
3938
```
40-
4139
1. Change to the newly created *acl-app* directory, and run the following command to build the project:
4240
4341
```dotnetcli
4442
dotnet build
4543
```
46-
4744
The build output should contain no warnings or errors.
48-
4945
```console
5046
Build succeeded.
5147
0 Warning(s)
@@ -60,15 +56,15 @@ Install the Confidential Ledger client library for .NET with [NuGet][client_nuge
6056
dotnet add package Azure.Security.ConfidentialLedger --version 1.0.0
6157
```
6258

63-
For this quickstart, you'll also need to install the Azure SDK client library for Azure Identity:
59+
For this quickstart, you also need to install the Azure SDK client library for Azure Identity:
6460

6561
```dotnetcli
6662
dotnet add package Azure.Identity
6763
```
6864

6965
## Object model
7066

71-
The Azure confidential ledger client library for .NET allows you to create an immutable ledger entry in the service. The [Code examples](#code-examples) section shows how to create a write to the ledger and retrieve the transaction ID.
67+
The Azure confidential ledger client library for .NET allows you to create an immutable ledger entry in the service. The [Code examples](#code-examples) section shows how to create a write to the ledger and retrieve the transaction ID.
7268

7369
## Code examples
7470

@@ -86,7 +82,7 @@ using Azure.Security.ConfidentialLedger.Certificate;
8682

8783
### Authenticate and create a client
8884

89-
In this quickstart, logged in user is used to authenticate to Azure confidential ledger, which is preferred method for local development. The name of your confidential ledger is expanded to the key vault URI, in the format "https://\<your-confidential-ledger-name\>.confidential-ledger.azure.com". This example is using ['DefaultAzureCredential()'](/dotnet/api/azure.identity.defaultazurecredential) class from [Azure Identity Library](/dotnet/api/overview/azure/identity-readme), which allows to use the same code across different environments with different options to provide identity.
85+
In this quickstart, logged in user is used to authenticate to Azure confidential ledger, which is preferred method for local development. The name of your confidential ledger is expanded to the key vault URI, in the format "https://\<your-confidential-ledger-name\>.confidential-ledger.azure.com". This example is using ['DefaultAzureCredential()'](/dotnet/api/azure.identity.defaultazurecredential) class from [Azure Identity Library](/dotnet/api/overview/azure/identity-readme), which allows to use the same code across different environments with different options to provide identity.
9086

9187
```csharp
9288
credential = DefaultAzureCredential()

articles/confidential-ledger/quickstart-portal.md

Lines changed: 7 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -3,15 +3,15 @@ title: Quickstart – Microsoft Azure confidential ledger with the Azure portal
33
description: Learn to use the Microsoft Azure confidential ledger through the Azure portal
44
author: msmbaldwin
55
ms.author: mbaldwin
6-
ms.date: 11/14/2022
6+
ms.date: 01/30/2024
77
ms.service: confidential-ledger
88
ms.topic: quickstart
99
ms.custom: mode-ui
1010
---
1111

1212
# Quickstart: Create a confidential ledger using the Azure portal
1313

14-
Azure confidential ledger is a cloud service that provides a high integrity store for sensitive data logs and records that require data to be kept intact. For more information on Azure confidential ledger, and for examples of what can be stored in a confidential ledger, see [About Microsoft Azure confidential ledger](overview.md).
14+
Azure confidential ledger is a cloud service that provides a high integrity store for sensitive data logs and records that require data to be kept intact. For more information on Azure confidential ledger and examples of what can be stored in a confidential ledger, see [About Microsoft Azure confidential ledger](overview.md).
1515

1616
[!INCLUDE [quickstarts-free-trial-note](../../includes/quickstarts-free-trial-note.md)]
1717

@@ -28,32 +28,25 @@ Sign in to the [Azure portal](https://portal.azure.com).
2828
## Create a confidential ledger
2929

3030
1. From the Azure portal menu, or from the Home page, select **Create a resource**.
31-
3231
1. In the Search box, enter "Confidential Ledger", select said application, and then choose **Create**.
33-
3432
1. On the Create confidential ledger section, provide the following information:
3533
- **Name**: Provide a unique name.
3634
- **Subscription**: Choose the desired subscription.
3735
- **Resource Group**: Select **Create new*** and enter a resource group name.
3836
- **Location**: In the pull-down menu, choose a location.
3937
- Leave the other options to their defaults.
40-
4138
1. Select the **Security** tab.
42-
43-
1. You must now add a Microsoft Entra ID-based or certificate-based user to your confidential ledger with a role of "Administrator." In this quickstart, we'll add a Microsoft Entra ID-based user. Select **+ Add Microsoft Entra ID-Based User**.
44-
39+
1. You must now add a Microsoft Entra ID-based or certificate-based user to your confidential ledger with a role of "Administrator." In this quickstart, you add a Microsoft Entra ID-based user. Select **+ Add Microsoft Entra ID-Based User**.
4540
1. You must add a Microsoft Entra ID-based or Certificate-based user. Search the right-hand pane for your email address. Select your row, and then choose **Select** at the bottom of the pane. Your user profile may already be in the Microsoft Entra ID-based user section, in which case you cannot add yourself again.
46-
4741
1. In the **Ledger Role** drop-down field, select **Administrator**.
42+
1. Select **Review + Create**. After validation, select **Create**.
4843

49-
1. Select **Review + Create**. After validation has passed, select **Create**.
50-
51-
When the deployment is complete. select **Go to resource**.
44+
When the deployment is complete, select **Go to resource**.
5245

5346
:::image type="content" source="./media/confidential-ledger-portal-quickstart.png" alt-text="ACL portal create screen":::
5447

55-
Take note of the two properties listed below:
56-
- **confidential ledger name**: In the example, it is "test-create-ledger-demo." You will use this name for other steps.
48+
Take note of these two properties:
49+
- **confidential ledger name**: In the example, it is "test-create-ledger-demo." Use this name for other steps.
5750
- **Ledger endpoint**: In the example, this endpoint is `https://test-create-ledger-demo.confidential-ledger.azure.net/`.
5851

5952
You will need these property names to transact with the confidential ledger from the data plane.

0 commit comments

Comments
 (0)