Merge pull request #288274 from normesta/normesta-reg-updates-14

Some SFI fixes

Author: JamesJBarnett

articles/storage/blobs/data-lake-storage-access-control.md

@@ -332,7 +332,7 @@ A GUID is shown if the entry represents a user and that user doesn't exist in Mi
 
 When you define ACLs for service principals, it's important to use the Object ID (OID) of the *service principal* for the app registration that you created. It's important to note that registered apps have a separate service principal in the specific Microsoft Entra tenant. Registered apps have an OID that's visible in the Azure portal, but the *service principal* has another (different) OID.
 Article	
-To get the OID for the service principal that corresponds to an app registration, you can use the `az ad sp show` command. Specify the Application ID as the parameter. Here's an example of obtaining the OID for the service principal that corresponds to an app registration with App ID = 18218b12-1895-43e9-ad80-6e8fc1ea88ce. Run the following command in the Azure CLI:
+To get the OID for the service principal that corresponds to an app registration, you can use the `az ad sp show` command. Specify the Application ID as the parameter. Here's an example of obtaining the OID for the service principal that corresponds to an app registration with App ID = 00001111-aaaa-2222-bbbb-3333cccc4444. Run the following command in the Azure CLI:
 
 ```azurecli
 az ad sp show --id 18218b12-1895-43e9-ad80-6e8fc1ea88ce --query objectId

includes/azure-storage-logs-properties-authentication.md

@@ -14,17 +14,17 @@
 |**authorization / denyAssignmentId** | The date in GUID format when access was denied by a deny assignment. <br> The deny assignment might be from Azure Blueprints or a managed application. <br> For more information on deny assignments, see [Understand Azure deny assignments](../articles/role-based-access-control/deny-assignments.md) |
 |**authorization / reason** | The reason for the authorization result of the request. <br> For example: `Policy`, `NoApplicablePolicy`, or `MissingAttributes` |
 |**authorization / result** | The authorization result of the request. <br> For example: `Granted` or `Denied` |
-|**authorization / roleAssignmentId** | The role assignment ID. <br> For example: `4e2521b7-13be-4363-aeda-111111111111`.|
-|**authorization / roleDefinitionId** | The role definition ID. <br> For example: `ba92f5b4-2d11-453d-a403-111111111111`.|
+|**authorization / roleAssignmentId** | The role assignment ID. <br> For example: `11bb11bb-cc22-dd33-ee44-55ff55ff55ff`.|
+|**authorization / roleDefinitionId** | The role definition ID. <br> For example: `00aa00aa-bb11-cc22-dd33-44ee44ee44ee`.|
 |**authorization / type** | The source of the authorization result for the request. <br> For example: `RBAC` or `ABAC` |
 |**principals / id** | The ID of the security principal. <br> For example: `a4711f3a-254f-4cfb-8a2d-111111111111`.|
 |**principals / type** | The type of security principal. <br> For example: `ServicePrincipal`. |
 |**properties / metricResponseType** | The response from the metrics transaction. <br> For examples, see the ResponseType metrics dimension for your storage service: <br> [blobs](../articles/storage/blobs/monitor-blob-storage-reference.md#metrics-dimensions) <br> [files](../articles/storage/files/storage-files-monitoring-reference.md#metrics-dimensions) <br> [queues](../articles/storage/queues/monitor-queue-storage-reference.md#metrics-dimensions) <br> [tables](../articles/storage/tables/monitor-table-storage-reference.md#metrics-dimensions) |
 |**properties / objectKey** | The path to the object being accessed. <br> For example: `samplestorageaccount/container1/blob.png`. |
-|**requester / appID** | The Open Authorization (OAuth) application ID that is used as the requester. <br> For example: `d3f7d5fe-e64a-4e4e-871d-333333333333`.|
+|**requester / appID** | The Open Authorization (OAuth) application ID that is used as the requester. <br> For example: `00001111-aaaa-2222-bbbb-3333cccc4444`.|
 |**requester / audience** | The OAuth audience of the request. <br> For example: `https://storage.azure.com`. |
-|**requester / objectId** | The OAuth object ID of the requester. In case of Kerberos authentication, represents the object identifier of Kerberos authenticated user. <br> For example: `0e0bf547-55e5-465c-91b7-2873712b249c`. |
-|**requester / tenantId** | The OAuth tenant ID of identity. <br> For example: `72f988bf-86f1-41af-91ab-222222222222`.|
+|**requester / objectId** | The OAuth object ID of the requester. In case of Kerberos authentication, represents the object identifier of Kerberos authenticated user. <br> For example: `aaaaaaaa-0000-1111-2222-bbbbbbbbbbbb`. |
+|**requester / tenantId** | The OAuth tenant ID of identity. <br> For example: `aaaabbbb-0000-cccc-1111-dddd2222eeee`.|
 |**requester / tokenIssuer** | The OAuth token issuer. <br> For example: `https://sts.windows.net/72f988bf-86f1-41af-91ab-222222222222/`.|
 |**requester / upn** | The User Principal Name (UPN) of requestor. <br> For example: `[email protected]`. |
 |**requester / userName** | This field is reserved for internal use only.|

includes/azure-storage-logs-properties-operation.md

@@ -9,7 +9,7 @@
 | Property | Description |
 |:--- |:---|
 |**time** | The Universal Time Coordinated (UTC) time when the request was received by storage. For example: `2018/11/08 21:09:36.6900118`.|
-|**resourceId** | The resource ID of the storage account. For example: `/subscriptions/208841be-a4v3-4234-9450-08b90c09f4/resourceGroups/`<br>`myresourcegroup/providers/Microsoft.Storage/storageAccounts/mystorageaccount/storageAccounts/blobServices/default`|
+|**resourceId** | The resource ID of the storage account. For example: `/subscriptions/aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e/resourceGroups/`<br>`myresourcegroup/providers/Microsoft.Storage/storageAccounts/mystorageaccount/storageAccounts/blobServices/default`|
 |**category** | The category of the requested operation. For example: `StorageRead`, `StorageWrite`, or `StorageDelete`.|
 |**operationName** | The type of REST operation that was performed. <br> For a complete list of operations, see [Storage Analytics Logged Operations and Status Messages topic](/rest/api/storageservices/storage-analytics-logged-operations-and-status-messages). |
 |**operationVersion** | The storage service version that was specified when the request was made. This is equivalent to the value of the **x-ms-version** header. For example: `2017-04-17`.|
@@ -18,7 +18,7 @@
 |**statusText** | The status of the requested operation.  For a complete list of status messages, see [Storage Analytics Logged Operations and Status Messages topic](/rest/api/storageservices/storage-analytics-logged-operations-and-status-messages). In version 2017-04-17 and later, the status message `ClientOtherError` isn't used. Instead, this field contains an error code. For example: `SASSuccess`  |
 |**durationMs** | The total time, expressed in milliseconds, to perform the requested operation. This includes the time to read the incoming request, and to send the response to the requester. For example: `12`.|
 |**callerIpAddress** | The IP address of the requester, including the port number. For example: `192.100.0.102:4362`. |
-|**correlationId** | The ID that is used to correlate logs across resources. For example: `b99ba45e-a01e-0042-4ea6-772bbb000000`. |
+|**correlationId** | The ID that is used to correlate logs across resources. For example: `aaaa0000-bb11-2222-33cc-444444dddddd`. |
 |**location** | The location of storage account. For example: `North Europe`. |
 |**protocol**|The protocol that is used in the operation. For example: `HTTP`, `HTTPS`, `SMB`, or `NFS`|
 | **uri** | Uniform resource identifier that is requested. |