Skip to content

Commit b18c10a

Browse files
authored
Merge pull request #110244 from MicrosoftDocs/repo_sync_working_branch
Resolve syncing conflicts from repo_sync_working_branch to master
2 parents be361d6 + ee4eb68 commit b18c10a

File tree

11 files changed

+63
-46
lines changed

11 files changed

+63
-46
lines changed

articles/active-directory-b2c/secure-rest-api.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -268,7 +268,7 @@ To support bearer token authentication in your custom policy, modify the REST AP
268268
1. Ensure you add the claim used above as an input claim:
269269

270270
```xml
271-
<InputClaim ClaimTyeReferenceId="bearerToken"/>
271+
<InputClaim ClaimTypeReferenceId="bearerToken"/>
272272
```
273273

274274
After you add the above snippets, your technical profile should look like the following XML code:
@@ -288,7 +288,7 @@ After you add the above snippets, your technical profile should look like the fo
288288
<Item Key="AllowInsecureAuthInProduction">false</Item>
289289
</Metadata>
290290
<InputClaims>
291-
<InputClaim ClaimTyeReferenceId="bearerToken"/>
291+
<InputClaim ClaimTypeReferenceId="bearerToken"/>
292292
</InputClaims>
293293
...
294294
</TechnicalProfile>

articles/active-directory/authentication/concept-authentication-passwordless.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -159,7 +159,7 @@ Use the following table to choose which method will support your requirements an
159159

160160
## Next steps
161161

162-
[Enable FIDO2 security key passwordlesss options in your organization](howto-authentication-passwordless-security-key.md)
162+
[Enable FIDO2 security key passwordless options in your organization](howto-authentication-passwordless-security-key.md)
163163

164164
[Enable phone-based passwordless options in your organization](howto-authentication-passwordless-phone.md)
165165

articles/active-directory/hybrid/howto-troubleshoot-upn-changes.md

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -55,11 +55,11 @@ You can change a UPN by changing the prefix, suffix, or both.
5555

5656
5757
Or<br>
58-
58+
5959

6060
Change the user's UPN every time the primary email address for a user is updated. No matter the reason for the email change, the UPN must always be updated to match.
6161

62-
During the initial synchronization from Active Directory to Azure AD, ensure the users' emails are identical to their UPNs
62+
During the initial synchronization from Active Directory to Azure AD, ensure the users' emails are identical to their UPNs.
6363

6464
### UPNs in Active Directory
6565

@@ -97,15 +97,15 @@ If the value of the userPrincipalName attribute doesn't correspond to a verified
9797

9898
### Roll-out bulk UPN changes
9999

100-
Follow the[best practices for a pilot](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-deployment-plans) for bulk UPN changes. Also have a tested rollback plan for reverting UPNs if you find issues that can't be quickly resolved. Once your pilot is running, you can start targeting small sets of users with various organizational roles and their specific sets of apps or devices.
100+
Follow the [best practices for a pilot](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-deployment-plans) for bulk UPN changes. Also have a tested rollback plan for reverting UPNs if you find issues that can't be quickly resolved. Once your pilot is running, you can start targeting small sets of users with various organizational roles and their specific sets of apps or devices.
101101

102102
Going through this first subset of users will give you a good idea of what users should expect as part of the change. Include this information on your user communications.
103103

104104
Create a defined procedure for changing UPNs on individual users as part of normal operations. We recommend having a tested procedure that includes documentation about known issues and workarounds.
105105

106106
The following sections detail potential known issues and workarounds when UPNs are changed.
107107

108-
## user provisioning known issues and workarounds
108+
## Apps known issues and workarounds
109109

110110
[Software as a service (SaaS)](https://azure.microsoft.com/overview/what-is-saas/) and Line of Business (LoB) applications often rely on UPNs to find users and store user profile information, including roles. Applications that use [Just in Time provisioning](https://docs.microsoft.com/azure/active-directory/app-provisioning/user-provisioning) to create a user profile when users sign in to the app for the first time can be affected by UPN changes.
111111

@@ -114,6 +114,7 @@ Changing a user's UPN could break the relationship between the Azure AD user and
114114

115115
**Workaround**<br>
116116
[Azure AD Automated User Provisioning](https://docs.microsoft.com/azure/active-directory/manage-apps/user-provisioning) lets you automatically create, maintain, and remove your user identities in supported cloud applications. Configuring automated user provisioning on your applications automatically updates UPNs on the applications. Test the applications as part of the progressive rollout to validate that they are not impacted by UPN changes.
117+
If you are a developer, consider [adding SCIM support to your application](https://docs.microsoft.com/azure/active-directory/app-provisioning/use-scim-to-provision-users-and-groups) to enable automatic user provisioning from Azure Active Directory.
117118

118119
## Managed devices known issues and workarounds
119120

@@ -127,7 +128,7 @@ By [bringing your devices to Azure AD](https://docs.microsoft.com/azure/active-d
127128
Users may experience single sign-on issues with applications that depend on Azure AD for authentication.
128129

129130
**Workaround** <br>
130-
Allow enough time for the UPN change to sync to Azure AD. Once you verify that the new UPN is reflected on the Azure AD Portal, ask the user to select the "Other user" tile to sign in with their new UPN. you can also verify through [PowerShell](https://docs.microsoft.com/powershell/module/azuread/get-azureaduser?view=azureadps-2.0). After signing in with their new UPN, references to the old UPN might still appear on "Access work or school" Windows setting.
131+
Allow enough time for the UPN change to sync to Azure AD. Once you verify that the new UPN is reflected on the Azure AD Portal, ask the user to select the "Other user" tile to sign in with their new UPN. You can also verify through [PowerShell](https://docs.microsoft.com/powershell/module/azuread/get-azureaduser?view=azureadps-2.0). After signing in with their new UPN, references to the old UPN might still appear on the "Access work or school" Windows setting.
131132

132133
![Screenshot of verified domains](./media/howto-troubleshoot-upn-changes/other-user.png)
133134

@@ -152,7 +153,8 @@ To unjoin a device from Azure AD, run the following command at a command prompt:
152153

153154
**dsregcmd /leave**
154155

155-
The user will need to [re-enroll](https://docs.microsoft.com/windows/security/identity-protection/hello-for-business/hello-hybrid-cert-whfb-provision) for Windows Hello for Business if it's being used. Windows 7 and 8.1 devices are not affected by this issue after UPN changes.
156+
The user will need to [re-enroll](https://docs.microsoft.com/windows/security/identity-protection/hello-for-business/hello-hybrid-cert-whfb-provision) for Windows Hello for Business if it's being used.
157+
Windows 7 and 8.1 devices are not affected by this issue after UPN changes.
156158

157159
## Microsoft Authenticator known issues and workarounds
158160

@@ -164,23 +166,21 @@ The [Microsoft Authenticator app](https://docs.microsoft.com/azure/active-direct
164166

165167
* Act as an Authentication Broker on iOS and Android devices to provide single sign-on for applications that use [Brokered authentication](https://docs.microsoft.com/azure/active-directory/develop/brokered-auth)
166168

167-
* Device registration (also known as Workplace Joined) to Azure AD, which is a requirement for other features like Intune App Protection and Device Enrolment/Management,
169+
* Device registration (also known as Workplace Join) to Azure AD, which is a requirement for other features like Intune App Protection and Device Enrolment/Management,
168170

169171
* Phone sign in, which requires MFA and device registration.
170172

171173
### Multi-Factor Authentication with Android devices
172174

173175
The Microsoft Authenticator app offers an out-of-band verification option. Instead of placing an automated phone call or SMS to the user during sign-in, [Multi-Factor Authentication (MFA)](https://docs.microsoft.com/azure/active-directory/authentication/concept-mfa-howitworks) pushes a notification to the Microsoft Authenticator app on the user's smartphone or tablet. The user simply taps Approve (or enters a PIN or biometric and taps "Authenticate") in the app to complete their sign-in.
174176

175-
When you change a user's UPN, mobile devices can experience the following issues:
176-
177177
**Known issues**
178178

179-
The old UPN still displays on the user account and a notification might not be received. [Verification codes](https://docs.microsoft.com/azure/active-directory/user-help/user-help-auth-app-faq) continue to work.
179+
When you change a user's UPN, the old UPN still displays on the user account and a notification might not be received. [Verification codes](https://docs.microsoft.com/azure/active-directory/user-help/user-help-auth-app-faq) continue to work.
180180

181181
**Workaround**
182182

183-
If a notification is received, instruct the user to dismiss the notification, open the Authenticator app, tap the "Check for notifications" option and approve the MFA prompt. After this, the UPN displayed on the account will be updated. Note the updated UPN might be displayed as a new account, this is due to other Authenticator functionality being used. For more information additional known issues in this article.
183+
If a notification is received, instruct the user to dismiss the notification, open the Authenticator app, tap the "Check for notifications" option and approve the MFA prompt. After this, the UPN displayed on the account will be updated. Note the updated UPN might be displayed as a new account, this is due to other Authenticator functionality being used. For more information refer to the additional known issues in this article.
184184

185185
### Brokered authentication
186186

articles/azure-resource-manager/templates/template-functions-resource.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -438,12 +438,12 @@ Returns an object representing a resource's runtime state.
438438
| Parameter | Required | Type | Description |
439439
|:--- |:--- |:--- |:--- |
440440
| resourceName or resourceIdentifier |Yes |string |Name or unique identifier of a resource. When referencing a resource in the current template, provide only the resource name as a parameter. When referencing a previously deployed resource or when the name of the resource is ambiguous, provide the resource ID. |
441-
| apiVersion |No |string |API version of the specified resource. Include this parameter when the resource isn't provisioned within same template. Typically, in the format, **yyyy-mm-dd**. For valid API versions for your resource, see [template reference](/azure/templates/). |
441+
| apiVersion |No |string |API version of the specified resource. **This parameter is required when the resource isn't provisioned within same template.** Typically, in the format, **yyyy-mm-dd**. For valid API versions for your resource, see [template reference](/azure/templates/). |
442442
| 'Full' |No |string |Value that specifies whether to return the full resource object. If you don't specify `'Full'`, only the properties object of the resource is returned. The full object includes values such as the resource ID and location. |
443443

444444
### Return value
445445

446-
Every resource type returns different properties for the reference function. The function doesn't return a single, predefined format. Also, the returned value differs based on whether you specified the full object. To see the properties for a resource type, return the object in the outputs section as shown in the example.
446+
Every resource type returns different properties for the reference function. The function doesn't return a single, predefined format. Also, the returned value differs based on the value of the `'Full'` argument. To see the properties for a resource type, return the object in the outputs section as shown in the example.
447447

448448
### Remarks
449449

@@ -508,7 +508,7 @@ When referencing a resource that is deployed in the same template, provide the n
508508
"value": "[reference(parameters('storageAccountName'))]"
509509
```
510510

511-
When referencing a resource that isn't deployed in the same template, provide the resource ID.
511+
When referencing a resource that isn't deployed in the same template, provide the resource ID and `apiVersion`.
512512

513513
```json
514514
"value": "[reference(resourceId(parameters('storageResourceGroup'), 'Microsoft.Storage/storageAccounts', parameters('storageAccountName')), '2018-07-01')]"

articles/azure-resource-manager/templates/template-tutorial-add-outputs.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,7 @@ az deployment group create \
7272

7373
---
7474

75-
In the output for the deployment command, you'll see an object similar to:
75+
In the output for the deployment command, you'll see an object similar to the following example only if the output is in JSON format:
7676

7777
```json
7878
{

articles/cdn/cdn-features.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -56,6 +56,7 @@ The following table compares the features available with each product.
5656
| [Token authentication](cdn-token-auth.md) | | | |**&#x2713;**|
5757
| [DDOS protection](https://www.us-cert.gov/ncas/tips/ST04-015) | **&#x2713;** |**&#x2713;** |**&#x2713;** |**&#x2713;** |
5858
| [Bring your own certificate](cdn-custom-ssl.md?tabs=option-2-enable-https-with-your-own-certificate#ssl-certificates) |**&#x2713;** | | **&#x2713;** | **&#x2713;** |
59+
| Supported TLS Versions | TLS 1.2, TLS 1.0/1.1 - [Configurable](https://docs.microsoft.com/rest/api/cdn/customdomains/enablecustomhttps#usermanagedhttpsparameters) | TLS 1.2 | TLS 1.2 | TLS 1.2 |
5960
||||
6061
| **Analytics and reporting** | **Standard Microsoft** | **Standard Akamai** | **Standard Verizon** | **Premium Verizon** |
6162
| [Azure diagnostic logs](cdn-azure-diagnostic-logs.md) | **&#x2713;** | **&#x2713;** |**&#x2713;** |**&#x2713;** |

articles/cognitive-services/LUIS/luis-language-support.md

Lines changed: 39 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -30,18 +30,25 @@ LUIS understands utterances in the following languages:
3030
| American English |`en-US` |||||
3131
| Arabic (preview - modern standard Arabic) |`ar-AR`|-|-|-|-|
3232
| *[Chinese](#chinese-support-notes) |`zh-CN` ||||-|
33-
| Dutch |`nl-NL` || - |-||
33+
| Dutch |`nl-NL` ||-|-||
3434
| French (France) |`fr-FR` |||||
35-
| French (Canada) |`fr-CA` |-| - |-||
35+
| French (Canada) |`fr-CA` |-|-|-||
3636
| German |`de-DE` |||||
37-
| Hindi | `hi-IN`|-|-|-|-|
37+
| Gujarati | `gu-IN`|-|-|-|-|
38+
| Hindi | `hi-IN`|-||-|-|
3839
| Italian |`it-IT` |||||
3940
| *[Japanese](#japanese-support-notes) |`ja-JP` ||||Key phrase only|
40-
| Korean |`ko-KR` || - |-|Key phrase only|
41+
| Korean |`ko-KR` ||-|-|Key phrase only|
42+
| Marathi | `mr-IN`|-|-|-|-|
4143
| Portuguese (Brazil) |`pt-BR` ||||not all sub-cultures|
4244
| Spanish (Spain) |`es-ES` |||||
43-
| Spanish (Mexico)|`es-MX` |-| - |||
44-
| Turkish | `tr-TR` ||-|-|Sentiment only|
45+
| Spanish (Mexico)|`es-MX` |-|-|||
46+
| Tamil | `ta-IN`|-|-|-|-|
47+
| Telugu | `te-IN`|-|-|-|-|
48+
| Turkish | `tr-TR` |||-|Sentiment only|
49+
50+
51+
4552

4653
Language support varies for [prebuilt entities](luis-reference-prebuilt-entities.md) and [prebuilt domains](luis-reference-prebuilt-domains.md).
4754

@@ -72,22 +79,28 @@ Hybrid languages combine words from two cultures such as English and Chinese. Th
7279
## Tokenization
7380
To perform machine learning, LUIS breaks an utterance into [tokens](luis-glossary.md#token) based on culture.
7481

75-
|Language| every space or special character | character level|compound words|[tokenized entity returned](luis-concept-data-extraction.md#tokenized-entity-returned)
76-
|--|:--:|:--:|:--:|:--:|
77-
|Arabic|||||
78-
|Chinese|||||
79-
|Dutch|||||
80-
|English (en-us)|||||
81-
|French (fr-FR)|||||
82-
|French (fr-CA)|||||
83-
|German|||||
84-
| Hindi ||-|-|-|-|
85-
|Italian|||||
86-
|Japanese|||||
87-
|Korean|||||
88-
|Portuguese (Brazil)|||||
89-
|Spanish (es-ES)|||||
90-
|Spanish (es-MX)|||||
82+
|Language| every space or special character | character level|compound words
83+
|--|:--:|:--:|:--:|
84+
|Arabic||||
85+
|Chinese||||
86+
|Dutch||||
87+
|English (en-us)||||
88+
|French (fr-FR)||||
89+
|French (fr-CA)||||
90+
|German||||
91+
|Gujarati||||
92+
|Hindi||||
93+
|Italian||||
94+
|Japanese|||✔
95+
|Korean||||
96+
|Marathi||||
97+
|Portuguese (Brazil)||||
98+
|Spanish (es-ES)||||
99+
|Spanish (es-MX)||||
100+
|Tamil||||
101+
|Telugu||||
102+
|Turkish||||
103+
91104

92105
### Custom tokenizer versions
93106

@@ -96,7 +109,10 @@ The following cultures have custom tokenizer versions:
96109
|Culture|Version|Purpose|
97110
|--|--|--|
98111
|German<br>`de-de`|1.0.0|Tokenizes words by splitting them using a machine learning-based tokenizer that tries to break down composite words into their single components.<br>If a user enters `Ich fahre einen krankenwagen` as an utterance, it is turned to `Ich fahre einen kranken wagen`. Allowing the marking of `kranken` and `wagen` independently as different entities.|
99-
|German<br>`de-de`|1.0.2|Tokenizes words by splitting them on spaces.<br> if a user enters `Ich fahre einen krankenwagen` as an utterance, it remains a single token. Thus `krankenwagen` is marked as a single entity. |
112+
|German<br>`de-de`|1.0.2|Tokenizes words by splitting them on spaces.<br> If a user enters `Ich fahre einen krankenwagen` as an utterance, it remains a single token. Thus `krankenwagen` is marked as a single entity. |
113+
|Dutch<br>`de-de`|1.0.0|Tokenizes words by splitting them using a machine learning-based tokenizer that tries to break down composite words into their single components.<br>If a user enters `Ik ga naar de kleuterschool` as an utterance, it is turned to `Ik ga naar de kleuter school`. Allowing the marking of `kleuter` and `school` independently as different entities.|
114+
|Dutch<br>`de-de`|1.0.1|Tokenizes words by splitting them on spaces.<br> If a user enters `Ik ga naar de kleuterschool` as an utterance, it remains a single token. Thus `kleuterschool` is marked as a single entity. |
115+
100116

101117
### Migrating between tokenizer versions
102118
<!--

articles/private-link/private-endpoint-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -140,7 +140,7 @@ For Azure services, use the recommended zone names as described in the following
140140
|Azure Relay (Microsoft.Relay/namespaces) | namespace |privatelink.servicebus.windows.net|
141141
|Azure Event Grid (Microsoft.EventGrid/topics) | topic | topic.{region}.privatelink.eventgrid.azure.net|
142142
|Azure Event Grid (Microsoft.EventGrid/domains) | domain | domain.{region}.privatelink.eventgrid.azure.net |
143-
|Azure WebApps(Microsoft.Web/sites) | site | privatelink.azurewebsites.net |
143+
|Azure WebApps (Microsoft.Web/sites) | site | privatelink.azurewebsites.net |
144144
|Azure Machine Learning(Microsoft.MachineLearningServices/workspaces) | workspace | privatelink.api.azureml.ms |
145145

146146
Azure will create a canonical name DNS record (CNAME) on the public DNS to redirect the resolution to the suggested domain names. You'll be able to override the resolution with the private IP address of your private endpoints.

articles/storage/blobs/storage-blob-event-quickstart.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -88,7 +88,7 @@ storageid=$(az storage account show --name <storage_account_name> --resource-gro
8888
endpoint=https://$sitename.azurewebsites.net/api/updates
8989
9090
az eventgrid event-subscription create \
91-
--resource-id $storageid \
91+
--source-resource-id $storageid \
9292
--name <event_subscription_name> \
9393
--endpoint $endpoint
9494
```

articles/stream-analytics/stream-analytics-window-functions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ Hopping window functions hop forward in time by a fixed period. It may be easy t
2929
![Stream Analytics hopping window](media/stream-analytics-window-functions/stream-analytics-window-functions-hopping-intro.png)
3030

3131
## Sliding window
32-
Sliding window functions, unlike Tumbling or Hopping windows, produce an output **only** when an event occurs. Every window will have at least one event and the window continuously moves forward by an (epsilon). Like hopping windows, events can belong to more than one sliding window.
32+
Sliding window functions, unlike Tumbling or Hopping windows, produce an output **only** when an event occurs. Every window will have at least one event and the window continuously moves forward by an ε (epsilon). Like hopping windows, events can belong to more than one sliding window.
3333

3434
![Stream Analytics sliding window](media/stream-analytics-window-functions/stream-analytics-window-functions-sliding-intro.png)
3535

0 commit comments

Comments
 (0)