Skip to content

Commit ac56ef0

Browse files
authored
Merge pull request #95262 from MicrosoftDocs/master
11/07 PM Publish
2 parents 018e3b4 + f694629 commit ac56ef0

File tree

842 files changed

+3590
-8779
lines changed

Some content is hidden

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

842 files changed

+3590
-8779
lines changed

.openpublishing.redirection.json

Lines changed: 190 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -770,6 +770,11 @@
770770
"redirect_url": "/azure/machine-learning/service",
771771
"redirect_document_id": false
772772
},
773+
{
774+
"source_path": "articles/cognitive-services/LUIS/luis-tutorial-prebuilt-intents-entities.md",
775+
"redirect_url": "/azure/cognitive-services/LUIS/tutorial-machine-learned-entity",
776+
"redirect_document_id": false
777+
},
773778
{
774779
"source_path": "articles/cognitive-services/LUIS/luis-quickstart-intents-only.md",
775780
"redirect_url": "/azure/cognitive-services/LUIS/tutorial-intents-only",
@@ -1220,6 +1225,61 @@
12201225
"redirect_url": "/azure/machine-learning/service/how-to-configure-environment",
12211226
"redirect_document_id": false
12221227
},
1228+
{
1229+
"source_path": "articles/frontdoor/waf-faq.md",
1230+
"redirect_url": "/azure/web-application-firewall/afds/waf-faq",
1231+
"redirect_document_id": false
1232+
},
1233+
{
1234+
"source_path": "articles/frontdoor/waf-front-door-rate-limit-powershell.md",
1235+
"redirect_url": "/azure/web-application-firewall/afds/waf-front-door-rate-limit-powershell",
1236+
"redirect_document_id": false
1237+
},
1238+
{
1239+
"source_path": "articles/frontdoor/waf-front-door-configure-ip-restriction.md",
1240+
"redirect_url": "/azure/web-application-firewall/afds/waf-front-door-configure-ip-restriction",
1241+
"redirect_document_id": false
1242+
},
1243+
{
1244+
"source_path": "articles/frontdoor/waf-front-door-configure-custom-response-code.md",
1245+
"redirect_url": "/azure/web-application-firewall/afds/waf-front-door-configure-custom-response-code",
1246+
"redirect_document_id": false
1247+
},
1248+
{
1249+
"source_path": "articles/frontdoor/waf-front-door-policy-configure-bot-protection.md",
1250+
"redirect_url": "/azure/web-application-firewall/afds/waf-front-door-policy-configure-bot-protection",
1251+
"redirect_document_id": false
1252+
},
1253+
{
1254+
"source_path": "articles/frontdoor/waf-front-door-custom-rules-powershell.md",
1255+
"redirect_url": "/azure/web-application-firewall/afds/waf-front-door-custom-rules-powershell",
1256+
"redirect_document_id": false
1257+
},
1258+
{
1259+
"source_path": "articles/frontdoor/waf-front-door-create-portal.md",
1260+
"redirect_url": "/azure/web-application-firewall/afds/waf-front-door-create-portal",
1261+
"redirect_document_id": false
1262+
},
1263+
{
1264+
"source_path": "articles/frontdoor/waf-front-door-monitor.md",
1265+
"redirect_url": "/azure/web-application-firewall/afds/waf-front-door-monitor",
1266+
"redirect_document_id": false
1267+
},
1268+
{
1269+
"source_path": "articles/frontdoor/waf-front-door-policy-settings.md",
1270+
"redirect_url": "/azure/web-application-firewall/afds/waf-front-door-policy-settings",
1271+
"redirect_document_id": false
1272+
},
1273+
{
1274+
"source_path": "articles/frontdoor/waf-front-door-custom-rules.md",
1275+
"redirect_url": "/azure/web-application-firewall/afds/waf-front-door-custom-rules",
1276+
"redirect_document_id": false
1277+
},
1278+
{
1279+
"source_path": "articles/frontdoor/waf-overview.md",
1280+
"redirect_url": "/azure/web-application-firewall/afds/afds-overview",
1281+
"redirect_document_id": false
1282+
},
12231283
{
12241284
"source_path": "articles/frontdoor/front-door-powershell-reference.md",
12251285
"redirect_url": "/powershell/module/azurerm.frontdoor",
@@ -34903,6 +34963,11 @@
3490334963
"redirect_url": "/azure/cognitive-services/Bing-Image-Search/language-support",
3490434964
"redirect_document_id": true
3490534965
},
34966+
{
34967+
"source_path": "articles/machine-learning/service/machine-learning-interpretability-explainability.md",
34968+
"redirect_url": "/azure/machine-learning/service/how-to-machine-learning-interpretability",
34969+
"redirect_document_id": true
34970+
},
3490634971
{
3490734972
"source_path": "articles/active-directory/identity-protection/overview-v2.md",
3490834973
"redirect_url": "/azure/active-directory/identity-protection/overview-identity-protection",
@@ -43827,6 +43892,131 @@
4382743892
"source_path": "articles/security/fundamentals/azure-log-integration-faq.md",
4382843893
"redirect_url": "/previous-versions/azure/security/fundamentals/azure-log-integration-faq",
4382943894
"redirect_document_id": false
43895+
},
43896+
{
43897+
"source_path": "articles/security/blueprints/au-protected-iaaswa-overview.md",
43898+
"redirect_url": "/previous-versions/azure/security/blueprints/au-protected-iaaswa-overview",
43899+
"redirect_document_id": false
43900+
},
43901+
{
43902+
"source_path": "articles/security/blueprints/au-protected-paaswa-overview.md",
43903+
"redirect_url": "/previous-versions/azure/security/blueprints/au-protected-paaswa-overview",
43904+
"redirect_document_id": false
43905+
},
43906+
{
43907+
"source_path": "articles/security/blueprints/azure-health.md",
43908+
"redirect_url": "/previous-versions/azure/security/blueprints/azure-health",
43909+
"redirect_document_id": false
43910+
},
43911+
{
43912+
"source_path": "articles/security/blueprints/fedramp-analytics-overview.md",
43913+
"redirect_url": "/previous-versions/azure/security/blueprints/fedramp-analytics-overview",
43914+
"redirect_document_id": false
43915+
},
43916+
{
43917+
"source_path": "articles/security/blueprints/fedramp-datawarehouse-overview.md",
43918+
"redirect_url": "/previous-versions/azure/security/blueprints/fedramp-datawarehouse-overview",
43919+
"redirect_document_id": false
43920+
},
43921+
{
43922+
"source_path": "articles/security/blueprints/fedramp-iaaswa-overview.md",
43923+
"redirect_url": "/previous-versions/azure/security/blueprints/fedramp-iaaswa-overview",
43924+
"redirect_document_id": false
43925+
},
43926+
{
43927+
"source_path": "articles/security/blueprints/fedramp-paaswa-overview.md",
43928+
"redirect_url": "/previous-versions/azure/security/blueprints/fedramp-paaswa-overview",
43929+
"redirect_document_id": false
43930+
},
43931+
{
43932+
"source_path": "articles/security/blueprints/ffiec-analytics-overview.md",
43933+
"redirect_url": "/previous-versions/azure/security/blueprints/ffiec-analytics-overview",
43934+
"redirect_document_id": false
43935+
},
43936+
{
43937+
"source_path": "articles/security/blueprints/ffiec-dw-overview.md",
43938+
"redirect_url": "/previous-versions/azure/security/blueprints/ffiec-dw-overview",
43939+
"redirect_document_id": false
43940+
},
43941+
{
43942+
"source_path": "articles/security/blueprints/ffiec-iaaswa-overview.md",
43943+
"redirect_url": "/previous-versions/azure/security/blueprints/ffiec-iaaswa-overview",
43944+
"redirect_document_id": false
43945+
},
43946+
{
43947+
"source_path": "articles/security/blueprints/ffiec-paaswa-overview.md",
43948+
"redirect_url": "/previous-versions/azure/security/blueprints/ffiec-paaswa-overview",
43949+
"redirect_document_id": false
43950+
},
43951+
{
43952+
"source_path": "articles/security/blueprints/nist171-analytics-overview.md",
43953+
"redirect_url": "/previous-versions/azure/security/blueprints/nist171-analytics-overview",
43954+
"redirect_document_id": false
43955+
},
43956+
{
43957+
"source_path": "articles/security/blueprints/nist171-datawarehouse-overview.md",
43958+
"redirect_url": "/previous-versions/azure/security/blueprints/nist171-datawarehouse-overview",
43959+
"redirect_document_id": false
43960+
},
43961+
{
43962+
"source_path": "articles/security/blueprints/nist171-iaaswa-overview.md",
43963+
"redirect_url": "/previous-versions/azure/security/blueprints/nist171-iaaswa-overview",
43964+
"redirect_document_id": false
43965+
},
43966+
{
43967+
"source_path": "articles/security/blueprints/nist171-paaswa-overview.md",
43968+
"redirect_url": "/previous-versions/azure/security/blueprints/nist171-paaswa-overview",
43969+
"redirect_document_id": false
43970+
},
43971+
{
43972+
"source_path": "articles/security/blueprints/pcidss-analytics-overview.md",
43973+
"redirect_url": "/previous-versions/azure/security/blueprints/pcidss-analytics-overview",
43974+
"redirect_document_id": false
43975+
},
43976+
{
43977+
"source_path": "articles/security/blueprints/pcidss-dw-overview.md",
43978+
"redirect_url": "/previous-versions/azure/security/blueprints/pcidss-dw-overview",
43979+
"redirect_document_id": false
43980+
},
43981+
{
43982+
"source_path": "articles/security/blueprints/pcidss-iaaswa-overview.md",
43983+
"redirect_url": "/previous-versions/azure/security/blueprints/pcidss-iaaswa-overview",
43984+
"redirect_document_id": false
43985+
},
43986+
{
43987+
"source_path": "articles/security/blueprints/pcidss-paaswa-overview.md",
43988+
"redirect_url": "/previous-versions/azure/security/blueprints/pcidss-paaswa-overview",
43989+
"redirect_document_id": false
43990+
},
43991+
{
43992+
"source_path": "articles/security/blueprints/uknhs-analytics-overview.md",
43993+
"redirect_url": "/previous-versions/azure/security/blueprints/uknhs-analytics-overview",
43994+
"redirect_document_id": false
43995+
},
43996+
{
43997+
"source_path": "articles/security/blueprints/uknhs-datawarehouse-overview.md",
43998+
"redirect_url": "/previous-versions/azure/security/blueprints/uknhs-datawarehouse-overview",
43999+
"redirect_document_id": false
44000+
},
44001+
{
44002+
"source_path": "articles/security/blueprints/uknhs-iaaswa-overview.md",
44003+
"redirect_url": "/previous-versions/azure/security/blueprints/uknhs-iaaswa-overview",
44004+
"redirect_document_id": false
44005+
},
44006+
{
44007+
"source_path": "articles/security/blueprints/uknhs-paaswa-overview.md",
44008+
"redirect_url": "/previous-versions/azure/security/blueprints/uknhs-paaswa-overview",
44009+
"redirect_document_id": false
44010+
},
44011+
{
44012+
"source_path": "articles/security/blueprints/ukofficial-iaaswa-overview.md",
44013+
"redirect_url": "/previous-versions/azure/security/blueprints/ukofficial-iaaswa-overview",
44014+
"redirect_document_id": false
44015+
},
44016+
{
44017+
"source_path": "articles/security/blueprints/ukofficial-paaswa-overview.md",
44018+
"redirect_url": "/previous-versions/azure/security/blueprints/ukofficial-paaswa-overview",
44019+
"redirect_document_id": false
4383044020
}
4383144021
]
4383244022
}

articles/active-directory/b2b/faq.md

Lines changed: 16 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ services: active-directory
66
ms.service: active-directory
77
ms.subservice: B2B
88
ms.topic: reference
9-
ms.date: 04/10/2019
9+
ms.date: 11/07/2019
1010

1111
ms.author: mimart
1212
author: msmimart
@@ -54,15 +54,21 @@ Absolutely. For more information, see [Adding guest users to a role](add-guest-t
5454
Unless a user is assigned the role of limited administrator, B2B collaboration users won't require access to the Azure portal. However, B2B collaboration users who are assigned the role of limited administrator can access the portal. Also, if a guest user who isn't assigned one of these admin roles accesses the portal, the user might be able to access certain parts of the experience. The guest user role has some permissions in the directory.
5555

5656
### Can I block access to the Azure portal for guest users?
57-
Yes! When you configure this policy, be careful to avoid accidentally blocking access to members and admins.
58-
To block a guest user's access to the [Azure portal](https://portal.azure.com), use a Conditional Access policy in the Windows Azure classic deployment model API:
59-
1. Modify the **All Users** group so that it contains only members.
60-
![Screenshot showing All Users group where UserType is not equal Guest](media/faq/modify-all-users-group.png)
61-
2. Create a dynamic group that contains guest users.
62-
![Screenshot showing a new All Guest Users group](media/faq/group-with-guest-users.png)
63-
3. Set up a Conditional Access policy to block guest users from accessing the portal, as shown in the following video:
64-
65-
> [!VIDEO https://channel9.msdn.com/Blogs/Azure/b2b-block-guest-user/Player]
57+
58+
Yes! You can create a Conditional Access policy that blocks all guest and external users from accessing the Azure portal. When you configure this policy, be careful to avoid accidentally blocking access to members and admins.
59+
60+
1. Sign in to your [Azure portal](https://portal.azure.com/) as a security administrator or a Conditional Access administrator.
61+
2. In the Azure portal, select **Azure Active Directory**.
62+
3. Under **Manage**, select **Security**.
63+
4. Under **Protect**, select **Conditional Access**. Select **New policy**.
64+
5. On the **New** page, in the **Name** textbox, enter a name for the policy (for example "Block guests from accessing the portal").
65+
6. Under **Assignments**, select **Users and groups**.
66+
7. On the **Include** tab, choose **Select users and groups**, and then select **All guest and external users (Preview)**.
67+
9. Select **Done**.
68+
10. On the **New** page, in the **Assignments** section, select **Cloud apps or actions**.
69+
11. On the **Cloud apps or actions** page, choose **Select apps**, and then choose **Select**.
70+
12. On the **Select** page, choose **Microsoft Azure Management**, and then choose **Select**.
71+
13. On the **Cloud apps or actions** page, select **Done**.
6672

6773
### Does Azure AD B2B collaboration support multi-factor authentication and consumer email accounts?
6874
Yes. Multi-factor authentication and consumer email accounts are both supported for Azure AD B2B collaboration.

articles/active-directory/conditional-access/faqs.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ Policies are enforced for business-to-business (B2B) collaboration users. Howeve
2929

3030
Yes. A SharePoint Online policy also applies to OneDrive for Business.
3131

32-
## Why can’t I set a policy on client apps, like Word or Outlook?
32+
## Why can’t I set a policy directly on client apps, like Word or Outlook?
3333

3434
A Conditional Access policy sets requirements for accessing a service. It's enforced when authentication to that service occurs. The policy is not set directly on a client application. Instead, it is applied when a client calls a service. For example, a policy set on SharePoint applies to clients calling SharePoint. A policy set on Exchange applies to Outlook.
3535

articles/active-directory/develop/quickstart-v2-javascript.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -79,11 +79,12 @@ Select the option that's suitable to your development environment:
7979

8080
* (Optional) To run the project with the IIS server, [download the Visual Studio project](https://github.com/Azure-Samples/active-directory-javascript-graphapi-v2/archive/vsquickstart.zip). Extract the zip file to a local folder (for example, *C:\Azure-Samples*).
8181

82+
#### Step 3: Configure your JavaScript app
83+
8284
> [!div renderon="docs"]
83-
> #### Step 3: Configure your JavaScript app
8485
> In the *JavaScriptSPA* folder, edit *index.html*, and set the `clientID` and `authority` values under `msalConfig`.
8586
86-
> [!div renderon="docs"]
87+
> [!div class="sxs-lookup" renderon="portal"]
8788
> In the *JavaScriptSPA* folder, edit *index.html*, and replace `msalConfig` with the following code:
8889
8990
```javascript
@@ -100,6 +101,10 @@ var msalConfig = {
100101
};
101102

102103
```
104+
> [!div renderon="portal"]
105+
> > [!NOTE]
106+
> > This quickstart supports Enter_the_Supported_Account_Info_Here.
107+
103108

104109
> [!div renderon="docs"]
105110
>
@@ -114,12 +119,7 @@ var msalConfig = {
114119
> > To find the values of **Application (client) ID**, **Directory (tenant) ID**, and **Supported account types**, go to the app's **Overview** page in the Azure portal.
115120
>
116121
117-
> [!div class="sxs-lookup" renderon="portal"]
118-
> #### Step 3: Your app is configured and ready to run
119-
> We have configured your project with values of your app's properties.
120-
121-
> [!div renderon="docs"]
122-
> #### Step 4: Run the project
122+
#### Step 4: Run the project
123123

124124
* If you're using [Node.js](https://nodejs.org/en/download/):
125125

articles/active-directory/develop/quickstart-v2-python-webapp.md

Lines changed: 22 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -71,6 +71,13 @@ To run this sample, you will need:
7171
> - Select a key duration of **In 1 year**.
7272
> - When you click on **Add**, the key value will be displayed.
7373
> - Copy the value of the key. You will need it later.
74+
> 1. Select the **API permissions** section
75+
>
76+
> - Click the **Add a permission** button and then,
77+
> - Ensure that the **Microsoft APIs** tab is selected
78+
> - In the *Commonly used Microsoft APIs* section, click on **Microsoft Graph**
79+
> - In the **Delegated permissions** section, ensure that the right permissions are checked: **User.ReadBasic.All**. Use the search box if necessary.
80+
> - Select the **Add permissions** button
7481
>
7582
> [!div class="sxs-lookup" renderon="portal"]
7683
>
@@ -80,9 +87,10 @@ To run this sample, you will need:
8087
>
8188
> 1. Add a reply URL as `http://localhost:5000/getAToken`.
8289
> 1. Create a Client Secret.
90+
> 1. Add Microsoft Graph API's User.ReadBasic.All delegated permission.
8391
>
8492
> > [!div renderon="portal" id="makechanges" class="nextstepaction"]
85-
> > [Make this change for me]()
93+
> > [Make these changes for me]()
8694
> > [!div id="appconfigured" class="alert alert-info"]
8795
> > ![Already configured](media/quickstart-v2-aspnet-webapp/green-check.png) Your application is configured with this attribute
8896
@@ -123,24 +131,24 @@ AUTHORITY = "https://login.microsoftonline.com/Enter_the_Tenant_Name_Here"
123131
python app.py
124132
```
125133
> [!IMPORTANT]
126-
> This quickstart application uses a client secret to identify itself as confidential client. Because the client secret is added as a plain-text to your project files, for security reasons, it is recommended that you use a certificate instead of a client secret before considering the application as production application. For more information on how to use a certificate, see [these instructions](https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-certificate-credentials).
134+
> This quickstart application uses a client secret to identify itself as confidential client. Because the client secret is added as a plain-text to your project files, for security reasons, it is recommended that you use a certificate instead of a client secret before considering the application as production application. For more information on how to use a certificate, see [these instructions](https://docs.microsoft.com/azure/active-directory/develop/active-directory-certificate-credentials).
127135
128-
## More information
136+
## More information
129137

130-
### Getting MSAL
131-
MSAL is the library used to sign in users and request tokens used to access an API protected by the Microsoft identity Platform.
132-
You can add MSAL Python to your application using Pip.
138+
### Getting MSAL
139+
MSAL is the library used to sign in users and request tokens used to access an API protected by the Microsoft identity Platform.
140+
You can add MSAL Python to your application using Pip.
133141

134-
```Shell
135-
pip install msal
136-
```
142+
```Shell
143+
pip install msal
144+
```
137145

138-
### MSAL initialization
139-
You can add the reference to MSAL Python by adding the following code to the top of the file where you will be using MSAL:
146+
### MSAL initialization
147+
You can add the reference to MSAL Python by adding the following code to the top of the file where you will be using MSAL:
140148

141-
```Python
142-
import msal
143-
```
149+
```Python
150+
import msal
151+
```
144152

145153
## Next steps
146154

articles/active-directory/fundamentals/add-users-azure-active-directory.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ ms.collection: M365-identity-device-management
1717
---
1818

1919
# Add or delete users using Azure Active Directory
20-
Add new users or delete existing users from your Azure Active Directory (Azure AD) organization.
20+
Add new users or delete existing users from your Azure Active Directory (Azure AD) organization. To add or delete users you must be a User administrator or Global administrator.
2121

2222
## Add a new user
2323
You can create a new user using the Azure Active Directory portal.

articles/active-directory/fundamentals/license-users-groups.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.service: active-directory
1010
ms.subservice: fundamentals
1111
ms.workload: identity
1212
ms.topic: conceptual
13-
ms.date: 09/18/2018
13+
ms.date: 09/06/2018
1414
ms.author: ajburnle
1515
ms.reviewer: jeffsta
1616
ms.custom: "it-pro, seodec18"
@@ -83,6 +83,8 @@ Make sure that anyone needing to use a licensed Azure AD service has the appropr
8383
1. Select **Assign**.
8484

8585
The user is added to the list of licensed users and has access to the included Azure AD services.
86+
> [!NOTE]
87+
> Licenses can also be assigned directly to a user from the user's **Licenses** page. If a user has a license assigned through a group membership and you want to assign the same license to the user directly, it can be done only from the **Products** page mentioned in step 1 only.
8688
8789
### To assign a license to a group
8890

0 commit comments

Comments
 (0)