Skip to content

Commit 87c6fca

Browse files
committed
Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into load-balancer-seo
2 parents f2a1f8f + b16bbda commit 87c6fca

File tree

4 files changed

+34
-22
lines changed

4 files changed

+34
-22
lines changed

articles/active-directory/develop/active-directory-configurable-token-lifetimes.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -49,11 +49,11 @@ Clients use access tokens to access a protected resource. An access token can be
4949

5050
### SAML tokens
5151

52-
SAML tokens are used by many web based SAAS applications, and are obtained using Azure Active Directory's SAML2 protocol endpoint. They are also consumed by applications using WS-Federation. The default lifetime of the token is 1 hour. After From and applications perspective the validity period of the token is specified by the NotOnOrAfter value of the <conditions …> element in the token. After the token validity period the client must initiate a new authentication request, which will often be satisfied without interactive sign in as a result of the Single Sign On (SSO) Session token.
52+
SAML tokens are used by many web based SAAS applications, and are obtained using Azure Active Directory's SAML2 protocol endpoint. They are also consumed by applications using WS-Federation. The default lifetime of the token is 1 hour. From an application's perspective, the validity period of the token is specified by the NotOnOrAfter value of the `<conditions …>` element in the token. After the validity period of the token has ended, the client must initiate a new authentication request, which will often be satisfied without interactive sign in as a result of the Single Sign On (SSO) Session token.
5353

54-
The value of NotOnOrAfter can be changed using the AccessTokenLifetime parameter in a TokenLifetimePolicy. It will be set to the lifetime configured in the policy if any, plus a clock skew factor of five minutes.
54+
The value of NotOnOrAfter can be changed using the `AccessTokenLifetime` parameter in a `TokenLifetimePolicy`. It will be set to the lifetime configured in the policy if any, plus a clock skew factor of five minutes.
5555

56-
Note that the subject confirmation NotOnOrAfter specified in the <SubjectConfirmationData> element is not affected by the Token Lifetime configuration.
56+
Note that the subject confirmation NotOnOrAfter specified in the `<SubjectConfirmationData>` element is not affected by the Token Lifetime configuration.
5757

5858
### Refresh tokens
5959

articles/governance/blueprints/concepts/deployment-stages.md

Lines changed: 23 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Stages of a blueprint deployment
33
description: Learn the steps the Azure Blueprint services goes through during a deployment.
4-
ms.date: 03/14/2019
4+
ms.date: 11/13/2019
55
ms.topic: conceptual
66
---
77
# Stages of a blueprint deployment
@@ -24,17 +24,24 @@ takes the following high-level steps:
2424
## Blueprints granted owner rights
2525

2626
The Azure Blueprints service principal is granted owner rights to the assigned subscription or
27-
subscriptions. The granted role allows Blueprints to create, and later revoke, the [system-assigned
28-
managed identity](../../../active-directory/managed-identities-azure-resources/overview.md).
27+
subscriptions when a [system-assigned managed
28+
identity](../../../active-directory/managed-identities-azure-resources/overview.md) managed identity
29+
is used. The granted role allows Blueprints to create, and later revoke, the **system-assigned**
30+
managed identity. If using a **user-assigned** managed identity, the Azure Blueprints service
31+
principal doesn't get and doesn't need owner rights on the subscription.
2932

3033
The rights are granted automatically if the assignment is done through the portal. However, if the
3134
assignment is done through the REST API, granting the rights needs to be done with a separate API
3235
call. The Azure Blueprint AppId is `f71766dc-90d9-4b7d-bd9d-4499c4331c3f`, but the service principal
33-
varies by tenant. Use [Azure Active Directory Graph API](../../../active-directory/develop/active-directory-graph-api.md)
36+
varies by tenant. Use
37+
[Azure Active Directory Graph API](../../../active-directory/develop/active-directory-graph-api.md)
3438
and REST endpoint [servicePrincipals](/graph/api/resources/serviceprincipal) to get the service
35-
principal. Then, grant the Azure Blueprints the _Owner_ role through the [Portal](../../../role-based-access-control/role-assignments-portal.md),
36-
[Azure CLI](../../../role-based-access-control/role-assignments-cli.md), [Azure PowerShell](../../../role-based-access-control/role-assignments-powershell.md),
37-
[REST API](../../../role-based-access-control/role-assignments-rest.md), or a [Resource Manager template](../../../role-based-access-control/role-assignments-template.md).
39+
principal. Then, grant the Azure Blueprints the _Owner_ role through the
40+
[Portal](../../../role-based-access-control/role-assignments-portal.md),
41+
[Azure CLI](../../../role-based-access-control/role-assignments-cli.md),
42+
[Azure PowerShell](../../../role-based-access-control/role-assignments-powershell.md),
43+
[REST API](../../../role-based-access-control/role-assignments-rest.md), or a
44+
[Resource Manager template](../../../role-based-access-control/role-assignments-template.md).
3845

3946
The Blueprints service doesn't directly deploy the resources.
4047

@@ -48,15 +55,20 @@ While creating the blueprint assignment, the type of [managed
4855
identity](../../../active-directory/managed-identities-azure-resources/overview.md) is selected. The
4956
default is a **system-assigned** managed identity. A **user-assigned** managed identity can be
5057
chosen. When using a **user-assigned** managed identity, it must be defined and granted permissions
51-
before the blueprint assignment is created.
58+
before the blueprint assignment is created. Both the
59+
[Owner](../../../role-based-access-control/built-in-roles.md#owner) and
60+
[Blueprint Operator](../../../role-based-access-control/built-in-roles.md#blueprint-operator)
61+
built-in roles have the necessary `blueprintAssignment/write` permission to create an assignment
62+
that uses a **user-assigned** managed identity.
5263

5364
## Optional - Blueprints creates system-assigned managed identity
5465

5566
When [system-assigned managed
5667
identity](../../../active-directory/managed-identities-azure-resources/overview.md) is selected
57-
during assignment, Blueprints creates the identity and grants the managed identity the [owner](../../../role-based-access-control/built-in-roles.md#owner)
58-
role. If an [existing assignment is upgraded](../how-to/update-existing-assignments.md), Blueprints
59-
uses the previously created managed identity.
68+
during assignment, Blueprints creates the identity and grants the managed identity the
69+
[owner](../../../role-based-access-control/built-in-roles.md#owner) role. If an
70+
[existing assignment is upgraded](../how-to/update-existing-assignments.md), Blueprints uses the
71+
previously created managed identity.
6072

6173
The managed identity related to the blueprint assignment is used to deploy or redeploy the resources
6274
defined in the blueprint. This design avoids assignments inadvertently interfering with each other.

articles/sentinel/connect-zscaler.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -103,7 +103,7 @@ In this step, you need to select the Linux machine that will act as a proxy betw
103103
- Port = 514
104104
- Format = CEF
105105
- IP address - make sure to send the CEF messages to the IP address of the virtual machine you dedicated for this purpose.
106-
For more information, see the [Zscaler Azure Sentinel integration guide](https://aka.ms/ZscalerCEFInstructions).
106+
For more information, see the [Zscaler and Azure Sentinel Deployment Guide](https://aka.ms/ZscalerCEFInstructions).
107107

108108
> [!NOTE]
109109
> This solution supports Syslog RFC 3164 or RFC 5424.

articles/storage/blobs/TOC.yml

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -539,11 +539,11 @@
539539
items:
540540
- name: Microsoft.Azure.Storage.Common (version 11.x)
541541
href: https://www.nuget.org/packages/Microsoft.Azure.Storage.Common/
542-
- name: Azure.Storage.Common (version 12.x - preview)
542+
- name: Azure.Storage.Common (version 12.x)
543543
href: https://www.nuget.org/packages/Azure.Storage.Common/
544544
- name: Microsoft.Azure.Storage.Blob (version 11.x)
545545
href: https://www.nuget.org/packages/Microsoft.Azure.Storage.Blob/
546-
- name: Azure.Storage.Blob (version 12.x - preview)
546+
- name: Azure.Storage.Blob (version 12.x)
547547
href: https://www.nuget.org/packages/Azure.Storage.Blobs/
548548
- name: Azure Configuration Manager
549549
href: https://www.nuget.org/packages/Microsoft.Azure.ConfigurationManager/
@@ -557,7 +557,7 @@
557557
items:
558558
- name: Azure Storage client library
559559
items:
560-
- name: Version 12.x (preview)
560+
- name: Version 12.x
561561
href: https://github.com/Azure/azure-sdk-for-net/tree/master/sdk/storage
562562
- name: Version 11.x and earlier
563563
href: https://github.com/Azure/azure-storage-net
@@ -567,19 +567,19 @@
567567
href: https://github.com/Azure/azure-sdk-for-net/tree/master/sdk/storage/Microsoft.Azure.Management.Storage
568568
- name: Java
569569
items:
570-
- name: Azure Storage client library version 12.x (preview)
570+
- name: Azure Storage client library version 12.x
571571
href: https://github.com/Azure/azure-sdk-for-java/tree/master/sdk/storage
572572
- name: Azure Storage client library version 8.x and earlier
573573
href: https://github.com/Azure/azure-storage-java
574574
- name: Node.js
575575
items:
576-
- name: Azure Storage client library version 12.x (preview)
576+
- name: Azure Storage client library version 12.x
577577
href: https://github.com/Azure/azure-sdk-for-js/tree/master/sdk/storage
578578
- name: Azure Storage client library version 10.x
579579
href: https://github.com/Azure/azure-storage-node
580580
- name: Python
581581
items:
582-
- name: Azure Storage client library version 12.x (preview)
582+
- name: Azure Storage client library version 12.x
583583
href: https://github.com/Azure/azure-sdk-for-python/tree/master/sdk/storage
584584
- name: Azure Storage client library version 2.1
585585
href: https://github.com/Azure/azure-storage-python
@@ -754,7 +754,7 @@
754754
- name: Storage Resource Provider
755755
href: /java/api/overview/azure/storage/management
756756
- name: JavaScript (version 12.x)
757-
href: /javascript/api/@azure/storage-blob/?view=azure-node-preview
757+
href: /javascript/api/@azure/storage-blob/
758758
- name: Python (version 12.x)
759759
href: /python/api/azure-storage-blob/
760760
- name: REST

0 commit comments

Comments
 (0)