Skip to content

Commit 468adc1

Browse files
2 parents 36fa6b9 + 882630e commit 468adc1

File tree

145 files changed

+2283
-909
lines changed

Some content is hidden

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

145 files changed

+2283
-909
lines changed

.openpublishing.redirection.json

Lines changed: 32 additions & 32 deletions
Original file line numberDiff line numberDiff line change
@@ -36465,57 +36465,57 @@
3646536465
},
3646636466
{
3646736467
"source_path": "articles/iot-central/core/concepts-connectivity-pnp.md",
36468-
"redirect_url": "/azure/iot-central/core/overview-iot-central-get-connected-pnp",
36468+
"redirect_url": "/azure/iot-central/preview/overview-iot-central-get-connected",
3646936469
"redirect_document_id": false
3647036470
},
3647136471
{
3647236472
"source_path": "articles/iot-central/core/concepts-stay-connected.md",
36473-
"redirect_url": "/azure/iot-central/core/overview-iot-central-stay-connected-pnp",
36473+
"redirect_url": "/azure/iot-central/preview/overview-iot-central-stay-connected",
3647436474
"redirect_document_id": false
3647536475
},
3647636476
{
3647736477
"source_path": "articles/iot-central/core/overview-iot-central-transform.md",
36478-
"redirect_url": "/azure/iot-central/core/overview-iot-central-transform-pnp",
36478+
"redirect_url": "/azure/iot-central/preview/overview-iot-central-transform",
3647936479
"redirect_document_id": false
3648036480
},
3648136481
{
3648236482
"source_path": "articles/iot-central/core/howto-create-event-rules-pnp.md",
36483-
"redirect_url": "/azure/iot-central/core/tutorial-create-telemetry-rules",
36483+
"redirect_url": "/azure/iot-central/preview/tutorial-create-telemetry-rules",
3648436484
"redirect_document_id": false
3648536485
},
3648636486
{
3648736487
"source_path": "articles/iot-central/core/howto-create-telemetry-rules-pnp.md",
36488-
"redirect_url": "/azure/iot-central/core/tutorial-create-telemetry-rules",
36488+
"redirect_url": "/azure/iot-central/preview/tutorial-create-telemetry-rules",
3648936489
"redirect_document_id": false
3649036490
},
3649136491
{
3649236492
"source_path": "articles/iot-central/core/tutorial-configure-rules-pnp.md",
36493-
"redirect_url": "/azure/iot-central/core/tutorial-create-telemetry-rules",
36493+
"redirect_url": "/azure/iot-central/preview/tutorial-create-telemetry-rules",
3649436494
"redirect_document_id": false
3649536495
},
3649636496
{
3649736497
"source_path": "articles/iot-central/core/tutorial-monitor-devices-pnp.md",
36498-
"redirect_url": "/azure/iot-central/core/quick-monitor-devices-pnp",
36498+
"redirect_url": "/azure/iot-central/preview/quick-monitor-devices",
3649936499
"redirect_document_id": false
3650036500
},
3650136501
{
3650236502
"source_path": "articles/iot-central/tutorial-add-device-pnp.md",
36503-
"redirect_url": "/azure/iot-central/core/quick-create-pnp-device-pnp",
36503+
"redirect_url": "/azure/iot-central/preview/quick-create-pnp-device",
3650436504
"redirect_document_id": false
3650536505
},
3650636506
{
3650736507
"source_path": "articles/iot-central/tutorial-define-device-type-pnp.md",
36508-
"redirect_url": "/azure/iot-central/core/quick-create-pnp-device-pnp",
36508+
"redirect_url": "/azure/iot-central/preview/quick-create-pnp-device",
3650936509
"redirect_document_id": false
3651036510
},
3651136511
{
3651236512
"source_path": "articles/iot-central/howto-export-data-blob-storage-pnp.md",
36513-
"redirect_url": "/azure/iot-central/core/howto-export-data-pnp",
36513+
"redirect_url": "/azure/iot-central/preview/howto-export-data",
3651436514
"redirect_document_id": false
3651536515
},
3651636516
{
3651736517
"source_path": "articles/iot-central/howto-export-data-event-hubs-service-bus-pnp.md",
36518-
"redirect_url": "/azure/iot-central/core/howto-export-data-pnp",
36518+
"redirect_url": "/azure/iot-central/preview/howto-export-data",
3651936519
"redirect_document_id": false
3652036520
},
3652136521
{
@@ -41985,7 +41985,7 @@
4198541985
},
4198641986
{
4198741987
"source_path": "articles/iot-central/concepts-architecture-pnp.md",
41988-
"redirect_url": "/azure/iot-central/core/concepts-architecture-pnp/",
41988+
"redirect_url": "/azure/iot-central/preview/concepts-architecture/",
4198941989
"redirect_document_id": true
4199041990
},
4199141991
{
@@ -41995,7 +41995,7 @@
4199541995
},
4199641996
{
4199741997
"source_path": "articles/iot-central/concepts-connectivity-pnp.md",
41998-
"redirect_url": "/azure/iot-central/core/concepts-connectivity-pnp/",
41998+
"redirect_url": "/azure/iot-central/preview/concepts-connectivity/",
4199941999
"redirect_document_id": true
4200042000
},
4200142001
{
@@ -42010,7 +42010,7 @@
4201042010
},
4201142011
{
4201242012
"source_path": "articles/iot-central/howto-administer-pnp.md",
42013-
"redirect_url": "/azure/iot-central/core/howto-administer-pnp/",
42013+
"redirect_url": "/azure/iot-central/preview/howto-administer/",
4201442014
"redirect_document_id": true
4201542015
},
4201642016
{
@@ -42035,7 +42035,7 @@
4203542035
},
4203642036
{
4203742037
"source_path": "articles/iot-central/howto-connect-devkit-pnp.md",
42038-
"redirect_url": "/azure/iot-central/core/howto-connect-devkit-pnp/",
42038+
"redirect_url": "/azure/iot-central/preview/howto-connect-devkit/",
4203942039
"redirect_document_id": true
4204042040
},
4204142041
{
@@ -42045,7 +42045,7 @@
4204542045
},
4204642046
{
4204742047
"source_path": "articles/iot-central/howto-connect-pnp-device-pnp.md",
42048-
"redirect_url": "/azure/iot-central/core/howto-connect-pnp-device-pnp/",
42048+
"redirect_url": "/azure/iot-central/preview/howto-connect-pnp-device/",
4204942049
"redirect_document_id": true
4205042050
},
4205142051
{
@@ -42100,7 +42100,7 @@
4210042100
},
4210142101
{
4210242102
"source_path": "articles/iot-central/howto-create-event-rules-pnp.md",
42103-
"redirect_url": "/azure/iot-central/core/tutorial-create-telemetry-rules-pnp/",
42103+
"redirect_url": "/azure/iot-central/preview/tutorial-create-telemetry-rules/",
4210442104
"redirect_document_id": true
4210542105
},
4210642106
{
@@ -42110,7 +42110,7 @@
4211042110
},
4211142111
{
4211242112
"source_path": "articles/iot-central/howto-create-telemetry-rules-pnp.md",
42113-
"redirect_url": "/azure/iot-central/core/tutorial-create-telemetry-rules-pnp",
42113+
"redirect_url": "/azure/iot-central/preview/tutorial-create-telemetry-rules",
4211442114
"redirect_document_id": true
4211542115
},
4211642116
{
@@ -42125,7 +42125,7 @@
4212542125
},
4212642126
{
4212742127
"source_path": "articles/iot-central/howto-customize-ui-pnp.md",
42128-
"redirect_url": "/azure/iot-central/core/howto-customize-ui-pnp/",
42128+
"redirect_url": "/azure/iot-central/preview/howto-customize-ui/",
4212942129
"redirect_document_id": true
4213042130
},
4213142131
{
@@ -42145,7 +42145,7 @@
4214542145
},
4214642146
{
4214742147
"source_path": "articles/iot-central/howto-manage-devices-pnp.md",
42148-
"redirect_url": "/azure/iot-central/core/howto-manage-devices-pnp/",
42148+
"redirect_url": "/azure/iot-central/preview/howto-manage-devices/",
4214942149
"redirect_document_id": true
4215042150
},
4215142151
{
@@ -42175,7 +42175,7 @@
4217542175
},
4217642176
{
4217742177
"source_path": "articles/iot-central/howto-manage-users-roles-pnp.md",
42178-
"redirect_url": "/azure/iot-central/core/howto-manage-users-roles-pnp/",
42178+
"redirect_url": "/azure/iot-central/preview/howto-manage-users-roles/",
4217942179
"redirect_document_id": true
4218042180
},
4218142181
{
@@ -42200,7 +42200,7 @@
4220042200
},
4220142201
{
4220242202
"source_path": "articles/iot-central/howto-set-up-template-pnp.md",
42203-
"redirect_url": "/azure/iot-central/core/howto-set-up-template-pnp/",
42203+
"redirect_url": "/azure/iot-central/preview/howto-set-up-template/",
4220442204
"redirect_document_id": true
4220542205
},
4220642206
{
@@ -42225,12 +42225,12 @@
4222542225
},
4222642226
{
4222742227
"source_path": "articles/iot-central/howto-use-device-groups-pnp.md",
42228-
"redirect_url": "/azure/iot-central/core/tutorial-use-device-groups-pnp/",
42228+
"redirect_url": "/azure/iot-central/preview/tutorial-use-device-groups/",
4222942229
"redirect_document_id": true
4223042230
},
4223142231
{
4223242232
"source_path": "articles/iot-central/core/howto-use-device-groups-pnp.md",
42233-
"redirect_url": "/azure/iot-central/core/tutorial-use-device-groups-pnp/",
42233+
"redirect_url": "/azure/iot-central/preview/tutorial-use-device-groups/",
4223442234
"redirect_document_id": true
4223542235
},
4223642236
{
@@ -42255,7 +42255,7 @@
4225542255
},
4225642256
{
4225742257
"source_path": "articles/iot-central/howto-version-device-template-pnp.md",
42258-
"redirect_url": "/azure/iot-central/core/howto-version-device-template-pnp/",
42258+
"redirect_url": "/azure/iot-central/preview/howto-version-device-template/",
4225942259
"redirect_document_id": true
4226042260
},
4226142261
{
@@ -42265,7 +42265,7 @@
4226542265
},
4226642266
{
4226742267
"source_path": "articles/iot-central/howto-view-bill-pnp.md",
42268-
"redirect_url": "/azure/iot-central/core/howto-view-bill-pnp/",
42268+
"redirect_url": "/azure/iot-central/preview/howto-view-bill/",
4226942269
"redirect_document_id": true
4227042270
},
4227142271
{
@@ -42285,7 +42285,7 @@
4228542285
},
4228642286
{
4228742287
"source_path": "articles/iot-central/overview-iot-central-pnp.md",
42288-
"redirect_url": "/azure/iot-central/core/overview-iot-central-pnp/",
42288+
"redirect_url": "/azure/iot-central/preview/overview-iot-central/",
4228942289
"redirect_document_id": true
4229042290
},
4229142291
{
@@ -42295,7 +42295,7 @@
4229542295
},
4229642296
{
4229742297
"source_path": "articles/iot-central/overview-iot-central-tour-pnp.md",
42298-
"redirect_url": "/azure/iot-central/core/overview-iot-central-tour-pnp/",
42298+
"redirect_url": "/azure/iot-central/preview/overview-iot-central-tour/",
4229942299
"redirect_document_id": true
4230042300
},
4230142301
{
@@ -42305,7 +42305,7 @@
4230542305
},
4230642306
{
4230742307
"source_path": "articles/iot-central/quick-create-pnp-device-pnp.md",
42308-
"redirect_url": "/azure/iot-central/core/quick-create-pnp-device-pnp/",
42308+
"redirect_url": "/azure/iot-central/preview/quick-create-pnp-device/",
4230942309
"redirect_document_id": true
4231042310
},
4231142311
{
@@ -42315,7 +42315,7 @@
4231542315
},
4231642316
{
4231742317
"source_path": "articles/iot-central/quick-deploy-iot-central-pnp.md",
42318-
"redirect_url": "/azure/iot-central/core/quick-deploy-iot-central-pnp/",
42318+
"redirect_url": "/azure/iot-central/preview/quick-deploy-iot-central/",
4231942319
"redirect_document_id": true
4232042320
},
4232142321
{
@@ -42330,7 +42330,7 @@
4233042330
},
4233142331
{
4233242332
"source_path": "articles/iot-central/tutorial-configure-rules-pnp.md",
42333-
"redirect_url": "/azure/iot-central/core/tutorial-create-telemetry-rules-pnp/",
42333+
"redirect_url": "/azure/iot-central/preview/tutorial-create-telemetry-rules/",
4233442334
"redirect_document_id": true
4233542335
},
4233642336
{
@@ -42350,7 +42350,7 @@
4235042350
},
4235142351
{
4235242352
"source_path": "articles/iot-central/tutorial-monitor-devices-pnp.md",
42353-
"redirect_url": "/azure/iot-central/core/quick-monitor-devices-pnp/",
42353+
"redirect_url": "/azure/iot-central/preview/quick-monitor-devices/",
4235442354
"redirect_document_id": true
4235542355
},
4235642356
{

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

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -156,6 +156,10 @@ The validators are described in this table:
156156

157157
The validators are all associated with properties of the `TokenValidationParameters` class, themselves initialized from the ASP.NET/ASP.NET Core configuration. In most cases, you won't have to change the parameters. There's one exception, for apps that aren't single tenants. (That is, web apps that accept users from any organization or from personal Microsoft accounts.) In this case, the issuer must be validated.
158158

159+
## Token validation in Azure Functions
160+
161+
It's also possible to validate incoming access tokens in Azure functions. You can find examples of validating tokens in Azure functions in [Dotnet](https://github.com/Azure-Samples/ms-identity-dotnet-webapi-azurefunctions), [NodeJS](https://github.com/Azure-Samples/ms-identity-nodejs-webapi-azurefunctions), and [Python](https://github.com/Azure-Samples/ms-identity-python-webapi-azurefunctions).
162+
159163
## Next steps
160164

161165
> [!div class="nextstepaction"]

articles/active-directory/users-groups-roles/groups-dynamic-membership.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -354,7 +354,10 @@ The custom property name can be found in the directory by querying a user's prop
354354

355355
## Rules for devices
356356

357-
You can also create a rule that selects device objects for membership in a group. You can't have both users and devices as group members. The **organizationalUnit** attribute is no longer listed and should not be used. This string is set by Intune in specific cases but is not recognized by Azure AD, so no devices are added to groups based on this attribute.
357+
You can also create a rule that selects device objects for membership in a group. You can't have both users and devices as group members.
358+
359+
> [!NOTE]
360+
> The **organizationalUnit** attribute is no longer listed and should not be used. This string is set by Intune in specific cases but is not recognized by Azure AD, so no devices are added to groups based on this attribute.
358361
359362
> [!NOTE]
360363
> systemlabels is a read-only attribute that cannot be set with Intune.
@@ -376,9 +379,8 @@ The following device attributes can be used.
376379
enrollmentProfileName | Apple Device Enrollment Profile, Device enrollment - Corporate device identifiers (Android - Kiosk), or Windows Autopilot profile name | (device.enrollmentProfileName -eq "DEP iPhones")
377380
isRooted | true false | (device.isRooted -eq true)
378381
managementType | MDM (for mobile devices)<br>PC (for computers managed by the Intune PC agent) | (device.managementType -eq "MDM")
379-
organizationalUnit | a valid on-premises organizational unit (OU) | (device.organizationalUnit -contains "laptop")
380382
deviceId | a valid Azure AD device ID | (device.deviceId -eq "d4fe7726-5966-431c-b3b8-cddc8fdb717d")
381-
objectId | a valid Azure AD object ID | (device.objectId -eq 76ad43c9-32c5-45e8-a272-7b58b58f596d")
383+
objectId | a valid Azure AD object ID | (device.objectId -eq "76ad43c9-32c5-45e8-a272-7b58b58f596d")
382384
devicePhysicalIds | any string value used by Autopilot, such as all Autopilot devices, OrderID, or PurchaseOrderID | (device.devicePhysicalIDs -any _ -contains "[ZTDId]") (device.devicePhysicalIds -any _ -eq "[OrderID]:179887111881") (device.devicePhysicalIds -any _ -eq "[PurchaseOrderId]:76222342342")
383385
systemLabels | any string matching the Intune device property for tagging Modern Workplace devices | (device.systemLabels -contains "M365Managed")
384386

articles/app-service/configure-ssl-certificate.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -320,7 +320,7 @@ Once the renew operation is complete, click **Sync**. The sync operation automat
320320
321321
### Export certificate
322322

323-
Because App Service Certificates is a [Key Vault secret](../key-vault/about-keys-secrets-and-certificates.md#key-vault-secrets), you can export a PFX copy of it and use it for other Azure services or outside of Azure.
323+
Because an App Service Certificate is a [Key Vault secret](../key-vault/about-keys-secrets-and-certificates.md#key-vault-secrets), you can export a PFX copy of it and use it for other Azure services or outside of Azure.
324324

325325
To export the App Service Certificate as a PFX file, run the following commands in the [Cloud Shell](https://shell.azure.com). You can also run it locally if you [installed Azure CLI](https://docs.microsoft.com/cli/azure/install-azure-cli). Replace the placeholders with the names you used when you [created the App Service certificate](#start-certificate-order).
326326

@@ -339,7 +339,7 @@ az keyvault secret download \
339339
--encoding base64
340340
```
341341

342-
The downloaded *appservicecertificate.pfx* file is a raw PKCS12 file that contains both the public and private certificates. Whenever you're prompted, both the import password and the PEM pass phrase are the empty string.
342+
The downloaded *appservicecertificate.pfx* file is a raw PKCS12 file that contains both the public and private certificates. In each prompt, use an empty string for the import password and the PEM pass phrase.
343343

344344
### Delete certificate
345345

articles/azure-functions/functions-networking-options.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -112,6 +112,12 @@ When you create a function app, you must create or link to a general-purpose Azu
112112

113113
[Learn more about storage account requirements.](./functions-create-function-app-portal.md#storage-account-requirements)
114114

115+
### Using Key Vault references
116+
117+
Key Vault references allow you to use secrets from Azure Key Vault in your Azure Functions application without requiring any code changes. Azure Key Vault is a service that provides centralized secrets management, with full control over access policies and audit history.
118+
119+
Currently [Key Vault references](../app-service/app-service-key-vault-references.md) will not work if your Key Vault is secured with service endpoints. To connect to a Key Vault using virtual network integration you will need to call key vault in your application code.
120+
115121
## Virtual network triggers (non-HTTP)
116122

117123
Currently, to use function triggers other than HTTP from within a virtual network, you must run your function app in an App Service plan or in an App Service Environment.

articles/azure-monitor/app/asp-net-core.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -209,7 +209,7 @@ For more information, see [Configure adaptive sampling for ASP.NET Core applicat
209209

210210
### Adding TelemetryInitializers
211211

212-
Use [telemetry initializers](https://docs.microsoft.com/azure/azure-monitor/app/api-filtering-sampling#add-properties-itelemetryinitializer) when you want to define global properties that are sent with all telemetry.
212+
Use [telemetry initializers](https://docs.microsoft.com/azure/azure-monitor/app/api-filtering-sampling#addmodify-properties-itelemetryinitializer) when you want to define global properties that are sent with all telemetry.
213213

214214
Add any new `TelemetryInitializer` to the `DependencyInjection` container as shown in the following code. The SDK automatically picks up any `TelemetryInitializer` that's added to the `DependencyInjection` container.
215215

articles/azure-monitor/app/asp-net-troubleshoot-no-data.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -171,7 +171,7 @@ You can disable it, but this is not recommended. Sampling is designed so that re
171171
On February 5 2018, we announced that we removed logging of the Client IP address. This does not affect Geo Location.
172172

173173
> [!NOTE]
174-
> If you need the first 3 octets of the IP address, you can use a [telemetry initializer](https://docs.microsoft.com/azure/application-insights/app-insights-api-filtering-sampling#add-properties-itelemetryinitializer) to add a custom attribute.
174+
> If you need the first 3 octets of the IP address, you can use a [telemetry initializer](https://docs.microsoft.com/azure/application-insights/app-insights-api-filtering-sampling#addmodify-properties-itelemetryinitializer) to add a custom attribute.
175175
> This does not affect data collected prior to February 5, 2018.
176176
177177
## Wrong geographical data in user telemetry

0 commit comments

Comments
 (0)