You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
61
61
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.
63
63
64
64
### UPNs in Active Directory
65
65
@@ -97,15 +97,15 @@ If the value of the userPrincipalName attribute doesn't correspond to a verified
97
97
98
98
### Roll-out bulk UPN changes
99
99
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.
101
101
102
102
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.
103
103
104
104
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.
105
105
106
106
The following sections detail potential known issues and workarounds when UPNs are changed.
107
107
108
-
## user provisioning known issues and workarounds
108
+
## Apps known issues and workarounds
109
109
110
110
[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.
111
111
@@ -114,6 +114,7 @@ Changing a user's UPN could break the relationship between the Azure AD user and
114
114
115
115
**Workaround**<br>
116
116
[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.
117
118
118
119
## Managed devices known issues and workarounds
119
120
@@ -127,7 +128,7 @@ By [bringing your devices to Azure AD](https://docs.microsoft.com/azure/active-d
127
128
Users may experience single sign-on issues with applications that depend on Azure AD for authentication.
128
129
129
130
**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.
131
132
132
133

133
134
@@ -152,7 +153,8 @@ To unjoin a device from Azure AD, run the following command at a command prompt:
152
153
153
154
**dsregcmd /leave**
154
155
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.
156
158
157
159
## Microsoft Authenticator known issues and workarounds
158
160
@@ -164,23 +166,21 @@ The [Microsoft Authenticator app](https://docs.microsoft.com/azure/active-direct
164
166
165
167
* 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)
166
168
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,
168
170
169
171
* Phone sign in, which requires MFA and device registration.
170
172
171
173
### Multi-Factor Authentication with Android devices
172
174
173
175
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.
174
176
175
-
When you change a user's UPN, mobile devices can experience the following issues:
176
-
177
177
**Known issues**
178
178
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.
180
180
181
181
**Workaround**
182
182
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.
Copy file name to clipboardExpand all lines: articles/azure-resource-manager/templates/template-functions-resource.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -438,12 +438,12 @@ Returns an object representing a resource's runtime state.
438
438
| Parameter | Required | Type | Description |
439
439
|:--- |:--- |:--- |:--- |
440
440
| 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/). |
442
442
| '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. |
443
443
444
444
### Return value
445
445
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.
447
447
448
448
### Remarks
449
449
@@ -508,7 +508,7 @@ When referencing a resource that is deployed in the same template, provide the n
|[Bring your own certificate](cdn-custom-ssl.md?tabs=option-2-enable-https-with-your-own-certificate#ssl-certificates)|**✓**||**✓**|**✓**|
| Portuguese (Brazil) |`pt-BR`|✔| ✔ |✔ |not all sub-cultures|
42
44
| 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
+
45
52
46
53
Language support varies for [prebuilt entities](luis-reference-prebuilt-entities.md) and [prebuilt domains](luis-reference-prebuilt-domains.md).
47
54
@@ -72,22 +79,28 @@ Hybrid languages combine words from two cultures such as English and Chinese. Th
72
79
## Tokenization
73
80
To perform machine learning, LUIS breaks an utterance into [tokens](luis-glossary.md#token) based on culture.
74
81
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
+
91
104
92
105
### Custom tokenizer versions
93
106
@@ -96,7 +109,10 @@ The following cultures have custom tokenizer versions:
96
109
|Culture|Version|Purpose|
97
110
|--|--|--|
98
111
|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. |
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.
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.
0 commit comments