Skip to content

Commit 34a6fa5

Browse files
authored
Merge pull request #113054 from MicrosoftDocs/master
4/28 AM Publish
2 parents 67bddb1 + ae70188 commit 34a6fa5

File tree

100 files changed

+844
-1399
lines changed

Some content is hidden

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

100 files changed

+844
-1399
lines changed

.openpublishing.redirection.json

Lines changed: 45 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -607,6 +607,46 @@
607607
"redirect_url": "/azure/virtual-machines/workloads/oracle/oracle-overview/",
608608
"redirect_document_id": false
609609
},
610+
{
611+
"source_path": "articles/machine-learning/studio/use-case-excel-studio.md",
612+
"redirect_url": "/azure/machine-learning/studio/",
613+
"redirect_document_id": false
614+
},
615+
{
616+
"source_path": "articles/machine-learning/studio/azure-ml-customer-churn-scenario.md",
617+
"redirect_url": "/azure/machine-learning/studio/",
618+
"redirect_document_id": false
619+
},
620+
{
621+
"source_path": "articles/machine-learning/studio/text-analytics-module-tutorial.md",
622+
"redirect_url": "/azure/machine-learning/studio/",
623+
"redirect_document_id": false
624+
},
625+
{
626+
"source_path": "articles/machine-learning/studio/extend-your-experiment-with-r.md",
627+
"redirect_url": "/azure/machine-learning/studio/",
628+
"redirect_document_id": false
629+
},
630+
{
631+
"source_path": "articles/machine-learning/studio/debug-models.md",
632+
"redirect_url": "/azure/machine-learning/studio/",
633+
"redirect_document_id": false
634+
},
635+
{
636+
"source_path": "articles/machine-learning/studio/troubleshooting-creating-ml-workspace.md",
637+
"redirect_url": "/azure/machine-learning/studio/",
638+
"redirect_document_id": false
639+
},
640+
{
641+
"source_path": "articles/machine-learning/studio/basics-infographic-with-algorithm-examples.md",
642+
"redirect_url": "/azure/machine-learning/how-to-select-algorithms",
643+
"redirect_document_id": false
644+
},
645+
{
646+
"source_path": "articles/machine-learning/studio/convert-training-experiment-to-scoring-experiment.md",
647+
"redirect_url": "/azure/machine-learning/studio/deploy-a-machine-learning-web-service",
648+
"redirect_document_id": false
649+
},
610650
{
611651
"source_path": "articles/machine-learning/studio/consume-web-service-with-web-app-template.md",
612652
"redirect_url": "/azure/machine-learning/studio/consume-web-services",
@@ -2832,6 +2872,11 @@
28322872
"redirect_url": "https://github.com/Azure-Samples/active-directory-dotnet-native-uwp-v2",
28332873
"redirect_document_id": false
28342874
},
2875+
{
2876+
"source_path": "articles/active-directory/develop/quickstart-v2-javascipt-auth-code.md",
2877+
"redirect_url": "/azure/active-directory/develop/quickstart-v2-javascript-auth-code",
2878+
"redirect_document_id": true
2879+
},
28352880
{
28362881
"source_path": "articles/active-directory/develop/active-directory-v2-devquickstarts-wpf.md",
28372882
"redirect_url": "https://docs.microsoft.com/azure/active-directory/develop/guidedsetups/active-directory-windesktop",

articles/active-directory/develop/scenario-web-app-call-api-app-configuration.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ public void ConfigureServices(IServiceCollection services)
4646
{
4747
// more code here
4848
49-
services.AddSignIn(Configuration, "AzureAd");
49+
services.AddSignIn(Configuration, "AzureAd")
5050
.AddWebAppCallsProtectedWebApi(Configuration,
5151
initialScopes: new string[] { "user.read" })
5252
.AddInMemoryTokenCaches();

articles/active-directory/governance/entitlement-management-troubleshoot.md

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -85,13 +85,19 @@ This article describes some items you should check to help you troubleshoot Azur
8585

8686
If the request has any delivery errors, the request status will be **Undelivered** or **Partially delivered**.
8787

88-
If there are any delivery errors, in the request's detail pane, there will be a count of delivery errors.
88+
If there are any delivery errors, a count of delivery errors will be displayed in the request's detail pane.
8989

9090
1. Click the count to see all of the request's delivery errors.
9191

9292
### Reprocess a request
9393

94-
If a request encounters an error, you can reprocess the request to try it again. You can only reprocess a request that has a status of **Delivery failed** or **Partially delivered** and a completed date of less than one week.
94+
If an error is met after triggering an access package reprocess request, you must wait while the system reprocesses the request. The system tries multiple times to reprocess for several hours, so you can't force reprocessing during this time.
95+
96+
You can only reprocess a request that has a status of **Delivery failed** or **Partially delivered** and a completed date of less than one week.
97+
98+
- If the error is fixed during the trials window, the request status will change to **Delivering**. The request will reprocess without additional actions from the user.
99+
100+
- If the error wasn't fixed during the trials window, the request status may be **Delivery failed** or **partially delivered**. You can then use the **reprocess** button. You'll have seven days to reprocess the request.
95101

96102
**Prerequisite role:** Global administrator, User administrator, Catalog owner, or Access package manager
97103

articles/active-directory/hybrid/choose-ad-authn.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -65,11 +65,11 @@ Details on decision questions:
6565

6666
1. Azure AD can handle sign-in for users without relying on on-premises components to verify passwords.
6767
2. Azure AD can hand off user sign-in to a trusted authentication provider such as Microsoft’s AD FS.
68-
3. If you need to apply user-level Active Directory security policies such as account expired, disabled account, password expired, account locked out, and sign-in hours on each user sign-in, Azure AD requires some on-premises components.
68+
3. If you need to apply, user-level Active Directory security policies such as account expired, disabled account, password expired, account locked out, and sign-in hours on each user sign-in, Azure AD requires some on-premises components.
6969
4. Sign-in features not natively supported by Azure AD:
7070
* Sign-in using smartcards or certificates.
7171
* Sign-in using on-premises MFA Server.
72-
* Sign-in using third party authentication solution.
72+
* Sign-in using third-party authentication solution.
7373
* Multi-site on-premises authentication solution.
7474
5. Azure AD Identity Protection requires Password Hash Sync regardless of which sign-in method you choose, to provide the *Users with leaked credentials* report. Organizations can fail over to Password Hash Sync if their primary sign-in method fails and it was configured before the failure event.
7575

@@ -128,7 +128,7 @@ Refer to [implementing pass-through authentication](../../active-directory/hybri
128128

129129
* **User experience**. The user experience of federated authentication depends on the implementation of the features, topology, and configuration of the federation farm. Some organizations need this flexibility to adapt and configure the access to the federation farm to suit their security requirements. For example, it's possible to configure internally connected users and devices to sign in users automatically, without prompting them for credentials. This configuration works because they already signed in to their devices. If necessary, some advanced security features make users' sign-in process more difficult.
130130

131-
* **Advanced scenarios**. A federated authentication solution is usually required when customers have an authentication requirement that Azure AD doesn't support natively. See detailed information to help you [choose the right sign-in option](https://blogs.msdn.microsoft.com/samueld/2017/06/13/choosing-the-right-sign-in-option-to-connect-to-azure-ad-office-365/). Consider the following common requirements:
131+
* **Advanced scenarios**. A federated authentication solution is required when customers have an authentication requirement that Azure AD doesn't support natively. See detailed information to help you [choose the right sign-in option](https://blogs.msdn.microsoft.com/samueld/2017/06/13/choosing-the-right-sign-in-option-to-connect-to-azure-ad-office-365/). Consider the following common requirements:
132132

133133
* Authentication that requires smartcards or certificates.
134134
* On-premises MFA servers or third-party multifactor providers requiring a federated identity provider.
@@ -197,7 +197,7 @@ Use or enable password hash synchronization for whichever authentication method
197197

198198
2. **On-premises outage survival**. The consequences of an on-premises outage due to a cyber-attack or disaster can be substantial, ranging from reputational brand damage to a paralyzed organization unable to deal with the attack. Recently, many organizations were victims of malware attacks, including targeted ransomware, which caused their on-premises servers to go down. When Microsoft helps customers deal with these kinds of attacks, it sees two categories of organizations:
199199

200-
* Organizations that previously turned on password hash synchronization changed their authentication method to use password hash synchronization. They were back online in a matter of hours. By using access to email via Office 365, they worked to resolve issues and access other cloud-based workloads.
200+
* Organizations that previously also turned on password hash synchronization on top of federated or pass-through authentication changed their primary authentication method to then use password hash synchronization. They were back online in a matter of hours. By using access to email via Office 365, they worked to resolve issues and access other cloud-based workloads.
201201

202202
* Organizations that didn’t previously enable password hash synchronization had to resort to untrusted external consumer email systems for communications to resolve issues. In those cases, it took them weeks to restore their on-premises identity infrastructure, before users were able to sign in to cloud-based apps again.
203203

articles/active-directory/hybrid/how-to-connect-pta-quick-start.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,7 @@ Ensure that the following prerequisites are in place.
6969
- For certificate validation, unblock the following URLs: **mscrl.microsoft.com:80**, **crl.microsoft.com:80**, **ocsp.msocsp.com:80**, and **www\.microsoft.com:80**. Since these URLs are used for certificate validation with other Microsoft products you may already have these URLs unblocked.
7070

7171
### Azure Government cloud prerequisite
72-
Prior to enabling Pass-through Authentication through Azure AD Connect with Step 2, download the latest release of the PTA agent from the Azure portal. You need to ensure that your agent is versions **x.x.xxx.x** or later. To verify your agent see [Upgrade authentication agents](how-to-connect-pta-upgrade-preview-authentication-agents.md)
72+
Prior to enabling Pass-through Authentication through Azure AD Connect with Step 2, download the latest release of the PTA agent from the Azure portal. You need to ensure that your agent is versions **1.5.1742.0.** or later. To verify your agent see [Upgrade authentication agents](how-to-connect-pta-upgrade-preview-authentication-agents.md)
7373

7474
After downloading the latest release of the agent, proceed with the below instructions to configure Pass-Through Authentication through Azure AD Connect.
7575

articles/active-directory/saas-apps/float-tutorial.md

Lines changed: 5 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -80,31 +80,16 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
8080

8181
1. On the **Basic SAML Configuration** section, if you wish to configure the application in **IDP** initiated mode, enter the values for the following fields:
8282

83-
a. In the **Identifier** text box, type any of the following URLs:
83+
a. In the **Identifier** text box, type this URL: `https://app.float.com/sso/metadata`.
8484

85-
| |
86-
|--|
87-
| `https://app.float.com/sso/metadata`|
88-
| `https://app.develop.float.com/sso/metadata`|
89-
90-
b. In the **Reply URL** text box, type a URL using any one of the following patterns:
91-
92-
| |
93-
|--|
94-
| `https://<hostname>.float.com/sso/azuread`|
95-
| `https://<hostname>.develop.float.com/sso/azuread`|
85+
b. In the **Reply URL** text box, type a URL using the pattern `https://<hostname>.float.com/sso/azuread`.
9686

9787
1. Click **Set additional URLs** and perform the following step if you wish to configure the application in **SP** initiated mode:
9888

99-
In the **Sign-on URL** text box, type a URL using any one of the following patterns:
100-
101-
| |
102-
|--|
103-
| `https://<hostname>.float.com/login`|
104-
| `https://<hostname>.develop.float.com/login`|
89+
In the **Sign-on URL** text box, type a URL in the pattern `https://<hostname>.float.com/login`.
10590

106-
> [!NOTE]
107-
> These values are not real. Update these values with the actual Identifier, Reply URL and Sign-on URL. Contact [Float Client support team](mailto:[email protected]) to get these values. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
91+
> [!NOTE]
92+
> These values are not real. Update these values with the actual Identifier, Reply URL and Sign-on URL. Contact [Float Client support team](mailto:[email protected]) to get these values. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
10893
10994
1. Float application expects the SAML assertions in a specific format, which requires you to add custom attribute mappings to your SAML token attributes configuration. The following screenshot shows the list of default attributes.
11095

articles/active-directory/users-groups-roles/TOC.yml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -155,19 +155,19 @@
155155
href: directory-assign-admin-roles.md
156156
- name: View and assign roles
157157
href: directory-manage-roles-portal.md
158-
- name: Custom role
158+
- name: Custom roles
159159
items:
160-
- name: Custom role
160+
- name: Custom roles
161161
href: roles-custom-overview.md
162-
- name: Create custom role
162+
- name: Create a custom role
163163
href: roles-create-custom.md
164164
- name: View custom role assignments
165165
href: roles-view-assignments.md
166166
- name: Assign roles in Azure AD admin center
167167
href: /azure/active-directory/fundamentals/active-directory-users-assign-role-azure-portal?context=azure/active-directory/users-groups-roles/context/ugr-context
168168
- name: Assign custom roles in PowerShell
169169
href: roles-assign-powershell.md
170-
- name: Custom rolpermissions
170+
- name: Custom role permissions
171171
href: roles-custom-available-permissions.md
172172
- name: Delegate app admin permissions
173173
href: roles-delegate-app-roles.md

articles/active-directory/users-groups-roles/directory-assign-admin-roles.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1818,12 +1818,12 @@ CRM Service Administrator | Dynamics 365 administrator | 44367163-eba1-44c3-98af
18181818
Customer LockBox Access Approver | Customer Lockbox access approver | 5c4f9dcd-47dc-4cf7-8c9a-9e4207cbfc91
18191819
Desktop Analytics Administrator | Desktop Analytics Administrator | 38a96431-2bdf-4b4c-8b6e-5d3d8abac1a4
18201820
Device Administrators | Device administrators | 9f06204d-73c1-4d4c-880a-6edb90606fd8
1821-
Device Join | Device join | 9c094953-4995-41c8-84c8-3ebb9b32c93f
1822-
Device Managers | Device managers | 2b499bcd-da44-4968-8aec-78e1674fa64d
1823-
Device Users | Device users | d405c6df-0af8-4e3b-95e4-4d06e542189e
1821+
Device Join | Deprecated | 9c094953-4995-41c8-84c8-3ebb9b32c93f
1822+
Device Managers | Deprecated | 2b499bcd-da44-4968-8aec-78e1674fa64d
1823+
Device Users | Deprecated | d405c6df-0af8-4e3b-95e4-4d06e542189e
18241824
Directory Readers | Directory readers | 88d8e3e3-8f55-4a1e-953a-9b9898b8876b
1825-
Directory Synchronization Accounts | Directory synchronization accounts | d29b2b05-8046-44ba-8758-1e26182fcf32
1826-
Directory Writers | Directory writers | 9360feb5-f418-4baa-8175-e2a00bac4301
1825+
Directory Synchronization Accounts | Not shown because it shouldn't be used | d29b2b05-8046-44ba-8758-1e26182fcf32
1826+
Directory Writers | Not shown because it shouldn't be used | 9360feb5-f418-4baa-8175-e2a00bac4301
18271827
Exchange Service Administrator | Exchange administrator | 29232cdf-9323-42fd-ade2-1d097af3e4de
18281828
External Identity Provider Administrator | External Identity Provider Administrator | be2f45a1-457d-42af-a067-6ec1fa63bc45
18291829
Global Reader | Global reader | f2ef992c-3afb-46b9-b7cf-a126ee74c451
@@ -1839,8 +1839,8 @@ Message Center Privacy Reader | Message center privacy reader | ac16e43d-7b2d-40
18391839
Message Center Reader | Message center reader | 790c1fb9-7f7d-4f88-86a1-ef1f95c05c1b
18401840
Network Administrator | Network administrator | d37c8bed-0711-4417-ba38-b4abe66ce4c2
18411841
Office Apps Administrator | Office apps administrator | 2b745bdf-0803-4d80-aa65-822c4493daac
1842-
Partner Tier1 Support | Partner tier1 support | 4ba39ca4-527c-499a-b93d-d9b492c50246
1843-
Partner Tier2 Support | Partner tier2 support | e00e864a-17c5-4a4b-9c06-f5b95a8d5bd8
1842+
Partner Tier1 Support | Not shown because it shouldn't be used | 4ba39ca4-527c-499a-b93d-d9b492c50246
1843+
Partner Tier2 Support | Not shown because it shouldn't be used | e00e864a-17c5-4a4b-9c06-f5b95a8d5bd8
18441844
Password Administrator | Password administrator | 966707d0-3269-4727-9be2-8c3a10f19b9d
18451845
Power BI Service Administrator | Power BI administrator | a9ea8996-122f-4c74-9520-8edcd192826c
18461846
Power Platform Administrator | Power platform administrator | 11648597-926c-4cf3-9c36-bcebb0ba8dcc
@@ -1860,9 +1860,9 @@ Teams Communications Administrator | Teams Communications Administrator | baf37b
18601860
Teams Communications Support Engineer | Teams Communications Support Engineer | f70938a0-fc10-4177-9e90-2178f8765737
18611861
Teams Communications Support Specialist | Teams Communications Support Specialist | fcf91098-03e3-41a9-b5ba-6f0ec8188a12
18621862
Teams Service Administrator | Teams Service Administrator | 69091246-20e8-4a56-aa4d-066075b2a7a8
1863-
User | User | a0b1b346-4d3e-4e8b-98f8-753987be4970
1863+
User | Not shown because it can't be used | a0b1b346-4d3e-4e8b-98f8-753987be4970
18641864
User Account Administrator | User administrator | fe930be7-5e62-47db-91af-98c3a49a38b1
1865-
Workplace Device Join | Workplace device join | c34f683f-4d5a-4403-affd-6615e00e3a7f
1865+
Workplace Device Join | Deprecated | c34f683f-4d5a-4403-affd-6615e00e3a7f
18661866

18671867
## Deprecated roles
18681868

articles/aks/TOC.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -252,7 +252,7 @@
252252
- name: View container data real-time
253253
href: ../azure-monitor/insights/container-insights-livedata-overview.md
254254
maintainContext: true
255-
- name: Use Windows Server containers (preview)
255+
- name: Use Windows Server containers
256256
items:
257257
- name: Create an AKS cluster
258258
href: windows-container-cli.md

0 commit comments

Comments
 (0)