Skip to content

Commit bf73d07

Browse files
committed
Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into FromPrivateRepo
2 parents dbd2d7a + 29189ac commit bf73d07

File tree

178 files changed

+2490
-3279
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

178 files changed

+2490
-3279
lines changed

.openpublishing.redirection.json

Lines changed: 116 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13691,7 +13691,17 @@
1369113691
},
1369213692
{
1369313693
"source_path": "articles/storage/common/storage-resource-manager-cannot-delete-storage-account-container-vhd.md",
13694-
"redirect_url": "/azure/storage/common/storage-monitoring-diagnosing-troubleshooting",
13694+
"redirect_url": "/azure/storage/blobs/storage-troubleshoot-vhds",
13695+
"redirect_document_id": false
13696+
},
13697+
{
13698+
"source_path": "articles/virtual-machines/linux/troubleshoot-vhds.md",
13699+
"redirect_url": "/azure/storage/blobs/storage-troubleshoot-vhds",
13700+
"redirect_document_id": false
13701+
},
13702+
{
13703+
"source_path": "articles/virtual-machines/windows/troubleshoot-vhds.md",
13704+
"redirect_url": "/azure/storage/blobs/storage-troubleshoot-vhds",
1369513705
"redirect_document_id": false
1369613706
},
1369713707
{
@@ -19104,6 +19114,111 @@
1910419114
"source_path": "articles/active-directory/develop/active-directory-v2-devquickstarts-webapp-webapi-dotnet.md",
1910519115
"redirect_url": "https://github.com/AzureADQuickStarts/AppModelv2-WebApp-WebAPI-OpenIDConnect-DotNet",
1910619116
"redirect_document_id": false
19117+
},
19118+
{
19119+
"source_path": "articles/active-directory/develop/active-directory-devquickstarts-webapp-java.md",
19120+
"redirect_url": "https://github.com/Azure-Samples/active-directory-java-webapp-openidconnect",
19121+
"redirect_document_id": false
19122+
},
19123+
{
19124+
"source_path": "articles/active-directory/develop/active-directory-devquickstarts-headless-java.md",
19125+
"redirect_url": "https://github.com/Azure-Samples/active-directory-java-native-headless",
19126+
"redirect_document_id": false
19127+
},
19128+
{
19129+
"source_path": "articles/security/blueprints/fedramp.md",
19130+
"redirect_url": "/azure/security/blueprints/fedramp-iaaswa-overview",
19131+
"redirect_document_id": true
19132+
},
19133+
{
19134+
"source_path": "articles/security/blueprints/fedramp-controls-overview.md",
19135+
"redirect_url": "/azure/security/blueprints/fedramp-iaaswa-controls-overview",
19136+
"redirect_document_id": true
19137+
},
19138+
{
19139+
"source_path": "articles/security/blueprints/fedramp-access-controls.md",
19140+
"redirect_url": "/azure/security/blueprints/fedramp-iaaswa-access-controls",
19141+
"redirect_document_id": true
19142+
},
19143+
{
19144+
"source_path": "articles/security/blueprints/fedramp-audit-accountability-controls.md",
19145+
"redirect_url": "/azure/security/blueprints/fedramp-iaaswa-audit-accountability-controls",
19146+
"redirect_document_id": true
19147+
},
19148+
{
19149+
"source_path": "articles/security/blueprints/fedramp-awareness-training-controls.md",
19150+
"redirect_url": "/azure/security/blueprints/fedramp-iaaswa-awareness-training-controls",
19151+
"redirect_document_id": true
19152+
},
19153+
{
19154+
"source_path": "articles/security/blueprints/fedramp-configuration-manager-controls.md",
19155+
"redirect_url": "/azure/security/blueprints/fedramp-iaaswa-configuration-management-controls",
19156+
"redirect_document_id": true
19157+
},
19158+
{
19159+
"source_path": "articles/security/blueprints/fedramp-contingency-planning-controls.md",
19160+
"redirect_url": "/azure/security/blueprints/cfedramp-iaaswa-ontingency-planning-controls",
19161+
"redirect_document_id": true
19162+
},
19163+
{
19164+
"source_path": "articles/security/blueprints/fedramp-identification-authentication-controls.md",
19165+
"redirect_url": "/azure/security/blueprints/fedramp-iaaswa-identification-authentication-controls",
19166+
"redirect_document_id": true
19167+
},
19168+
{
19169+
"source_path": "articles/security/blueprints/fedramp-incident-response-controls.md",
19170+
"redirect_url": "/azure/security/blueprints/fedramp-iaaswa-incident-response-controls",
19171+
"redirect_document_id": true
19172+
},
19173+
{
19174+
"source_path": "articles/security/blueprints/fedramp-maintenance-controls.md",
19175+
"redirect_url": "/azure/security/blueprints/fedramp-iaaswa-maintenance-controls",
19176+
"redirect_document_id": true
19177+
},
19178+
{
19179+
"source_path": "articles/security/blueprints/fedramp-media-protection-controls.md",
19180+
"redirect_url": "/azure/security/blueprints/fedramp-iaaswa-media-protection-controls",
19181+
"redirect_document_id": true
19182+
},
19183+
{
19184+
"source_path": "articles/security/blueprints/fedramp-personnel-security-controls.md",
19185+
"redirect_url": "/azure/security/blueprints/fedramp-iaaswa-personnel-security-controls",
19186+
"redirect_document_id": true
19187+
},
19188+
{
19189+
"source_path": "articles/security/blueprints/fedramp-physical-environmental-protection-controls.md",
19190+
"redirect_url": "/azure/security/blueprints/fedramp-iaaswa-physical-environmental-protection-controls",
19191+
"redirect_document_id": true
19192+
},
19193+
{
19194+
"source_path": "articles/security/blueprints/fedramp-planning-controls.md",
19195+
"redirect_url": "/azure/security/blueprints/fedramp-iaaswa-planning-controls",
19196+
"redirect_document_id": true
19197+
},
19198+
{
19199+
"source_path": "articles/security/blueprints/fedramp-risk-assessment-controls.md",
19200+
"redirect_url": "/azure/security/blueprints/fedramp-iaaswa-risk-assessment-controls",
19201+
"redirect_document_id": true
19202+
},
19203+
{
19204+
"source_path": "articles/security/blueprints/fedramp-security-assessment-authorization-controls.md",
19205+
"redirect_url": "/azure/security/blueprints/fedramp-iaaswa-security-assessment-authorization-controls",
19206+
"redirect_document_id": true
19207+
},
19208+
{
19209+
"source_path": "articles/security/blueprints/fedramp-system-communications-protection-controls.md",
19210+
"redirect_url": "/azure/security/blueprints/fedramp-iaaswa-system-communications-protection-controls",
19211+
"redirect_document_id": true
19212+
},
19213+
{
19214+
"source_path": "articles/security/blueprints/fedramp-system-information-integrity-controls.md",
19215+
"redirect_url": "/azure/security/blueprints/fedramp-iaaswa-system-information-integrity-controls",
19216+
"redirect_document_id": true
19217+
},
19218+
{
19219+
"source_path": "articles/security/blueprints/fedramp-system-services-acquisition-controls.md",
19220+
"redirect_url": "/azure/security/blueprints/fedramp-iaaswa-system-services-acquisition-controls",
19221+
"redirect_document_id": true
1910719222
}
1910819223
]
1910919224
}

articles/active-directory-b2c/basic-age-gating.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ ms.author: davidmu
1818
#Using age gating in Azure AD B2C
1919

2020
>[!IMPORTANT]
21-
>This feature is in private preview and only accessible through a separate URL. Do NOT use this on production directories, using these new features can result in data loss and may have unexpected changes in behavior until we go into general availability.
21+
>This feature is in private preview. Please see our [service blog](https://blogs.msdn.microsoft.com/azureadb2c/) for details as this becomes available, or contact [email protected]. Do NOT use this on production directories, using these new features can result in data loss and may have unexpected changes in behavior until we go into general availability.
2222
>
2323
2424
##Age gating

articles/active-directory-domain-services/active-directory-ds-troubleshoot-nsg.md

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,13 @@ This article helps you troubleshoot and resolve network-related configuration er
2626

2727
Invalid NSG configurations are the most common cause of network errors for Azure AD Domain Services. The Network Security Group (NSG) configured for your virtual network must allow access to [specific ports](active-directory-ds-networking.md#ports-required-for-azure-ad-domain-services). If these ports are blocked, Microsoft cannot monitor or update your managed domain. Additionally, synchronization between your Azure AD directory and your managed domain is impacted. While creating your NSG, keep these ports open to avoid interruption in service.
2828

29+
### Checking your NSG for compliance
30+
31+
1. Navigate to the [Network security groups](https://portal.azure.com/#blade/HubsExtension/Resources/resourceType/Microsoft.Network%2FNetworkSecurityGroups) page in the Azure portal
32+
2. From the table, choose the NSG associated with the subnet in which your managed domain is enabled.
33+
3. Under **Settings** in the left-hand panel, click **Inbound security rules**
34+
4. Review the rules in place and identify which rules are blocking access to [these ports](active-directory-ds-networking.md#ports-required-for-azure-ad-domain-services).
35+
5. Edit the NSG to ensure compliance by either deleting the rule, adding a rule, or creating a new NSG entirely. Steps to [add a rule](#add-a-rule-to-a-network-security-group-using-the-azure-portal) or [create a new, compliant NSG](#create-a-nsg-for-azure-ad-domain-services-using-powershell) are below.
2936

3037
## Sample NSG
3138
The following table depicts a sample NSG that would keep your managed domain secure while allowing Microsoft to monitor, manage, and update information.
@@ -45,7 +52,7 @@ If you do not want to use PowerShell, you can manually add single rules to NSGs
4552
5. Verify your rule has been created by locating it in the rules table.
4653

4754

48-
## Create an NSG for Azure AD Domain Services using PowerShell
55+
## Create a NSG for Azure AD Domain Services using PowerShell
4956
This NSG is configured to allow inbound traffic to the ports required by Azure AD Domain Services, while denying any other unwanted inbound access.
5057

5158
**Pre-requisite: Install and configure Azure PowerShell**

articles/active-directory/TOC.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -53,6 +53,7 @@
5353
#### [Invitation email](active-directory-b2b-invitation-email.md)
5454
#### [Invitation redemption](active-directory-b2b-redemption-experience.md)
5555
#### [Add B2B users without an invitation](active-directory-b2b-add-user-without-invite.md)
56+
#### [Allow or block invitations](active-directory-b2b-allow-deny-list.md)
5657
#### [Conditional access for B2B](active-directory-b2b-mfa-instructions.md)
5758
#### [B2B sharing policies](active-directory-b2b-delegate-invitations.md)
5859
#### [Add a B2B user to a role](active-directory-b2b-add-guest-to-role.md)

articles/active-directory/active-directory-application-proxy-tableau.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.workload: identity
1212
ms.tgt_pltfrm: na
1313
ms.devlang: na
1414
ms.topic: article
15-
ms.date: 04/26/2018
15+
ms.date: 05/02/2018
1616
ms.author: markvi
1717
ms.reviewer: harshja
1818
ms.custom: it-pro
@@ -28,7 +28,7 @@ Azure Active Directory Application Proxy and Tableau have partnered to ensure yo
2828

2929
The scenario in this article assumes that you have:
3030

31-
- [Tableau](https://onlinehelp.tableau.com/current/server/en-us/proxy.htm#reverse-proxy-server) configured.
31+
- [Tableau](https://onlinehelp.tableau.com/current/server/en-us/proxy.htm#azure) configured.
3232

3333
- An [Application Proxy connector](active-directory-application-proxy-enable.md) installed.
3434

articles/active-directory/active-directory-enterprise-app-role-management.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -117,7 +117,7 @@ If your application expects custom roles to be passed in SAML response, you need
117117
"origin": "ServicePrincipal",
118118
"value": "Administrator"
119119
}
120-
],
120+
]
121121
}
122122
```
123123
> [!Note]

articles/active-directory/active-directory-reporting-activity-sign-ins-errors.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ms.devlang: na
1313
ms.topic: get-started-article
1414
ms.tgt_pltfrm: na
1515
ms.workload: identity
16-
ms.date: 05/01/2018
16+
ms.date: 05/02/2018
1717
ms.author: markvi
1818
ms.reviewer: dhanyahk
1919

@@ -71,14 +71,15 @@ The following section provides you with a complete overview of all possible erro
7171
|50097|Device is not authenticated.|
7272
|50105|The signed in user is not assigned to a role for this application.|
7373
|50125|Sign-in was interrupted due to a password reset or password registration entry|
74-
|50126|Invalid username or password or Invalid on-premises username or password.|
74+
|50126|Invalid username or password or Invalid on-premise username or password.|
7575
|50127|User needs to install a broker app to gain access to this content.|
7676
|50129|Device is not Workplace joined - Workplace join is required to register the device.|
7777
|50131|Used in various conditional access errors. E.g Bad Windows device state, request blocked due to suspicious activity, access policy and security policy decisions.|
7878
|50133|Session is invalid due to expiration or recent password change.|
7979
|50140|User prompted for consent to keep them signed-in on the device|
8080
|50144|User's Active Directory password has expired.|
8181
|53000|Conditional Access policy requires a compliant device, and the device is not compliant.|
82+
|53003|Access has been blocked due to conditional access policies.|
8283
|65001|Application X doesn't have permission to access application Y or the permission has been revoked. Or The user or administrator has not consented to use the application with ID X. Send an interactive authorization request for this user and resource. Or The user or administrator has not consented to use the application with ID X. Send an authorization request to your tenant admin to act on behalf of the App : Y for Resource : Z.|
8384
|65005|The application required resource access list does not contain applications discoverable by the resource or The client application has requested access to resource which was not specified in its required resource access list or Graph service returned bad request or resource not found.|
8485
|70001|The application named X was not found in the tenant named Y. This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant. You might have sent your authentication request to the wrong tenant.|
@@ -103,7 +104,6 @@ The following section provides you with a complete overview of all possible erro
103104
|90014|Used in various cases when an expected field is not present in the credential.|
104105
|90093|Graph returned with forbidden error code for the request.|
105106
|90094|Admin consent is needed.|
106-
107107
## Next steps
108108

109109
For more details, see the [Sign-in activity reports in the Azure Active Directory portal](active-directory-reporting-activity-sign-ins.md).

0 commit comments

Comments
 (0)