[Az.DeviceRegistry] - add support for DeviceRegistry public preview API version 2025-07-01-preview #28291
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…+ aeps), lint existing files
…ult empty pages so far
mryanlo
requested review from
wyunchi-ms,
dolauli,
isra-fel,
VeryEarly,
YanaXu and
vidai-msft
as code owners
| Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status. |
There was a problem hiding this comment.
Pull Request Overview
This PR adds support for Device Registry service's public preview API version 2025-07-01-preview. It introduces PowerShell cmdlets for new resources while maintaining existing Asset, AssetEndpointProfile, and Billing functionality.
Key Changes
- Added Schema Registry resource management (Schema, Schema Version)
- Added Namespace resource management (Namespace, Namespace Asset, Namespace Device)
- Added Namespace Discovered resource management (Discovered Asset, Discovered Device)
- Added migration functionality for moving assets to namespaces
Reviewed Changes
Copilot reviewed 71 out of 186 changed files in this pull request and generated 4 comments.
Show a summary per file
| File | Description |
|---|---|
| New-AzDeviceRegistrySchema.md | Example documentation for creating Device Registry schemas |
| New-AzDeviceRegistry*.md (namespace resources) | Example documentation for new namespace-scoped resources |
| Get-AzDeviceRegistry*.md (various resources) | Example documentation for retrieving new resources |
| Update-AzDeviceRegistry*.md (schema resources) | Documentation for updating schema-related resources |
| Get-AzDeviceRegistryAsset.md | Minor example numbering correction |
| Move-AzDeviceRegistryNamespace.md | Documentation for asset migration functionality |
...iceRegistry/DeviceRegistry.Autorest/examples/New-AzDeviceRegistryNamespaceDiscoveredAsset.md
Outdated
Show resolved
Hide resolved
src/DeviceRegistry/DeviceRegistry.Autorest/examples/New-AzDeviceRegistryNamespaceDevice.md
Show resolved
Hide resolved
src/DeviceRegistry/DeviceRegistry.Autorest/examples/Get-AzDeviceRegistryNamespace.md
Outdated
Show resolved
Hide resolved
src/DeviceRegistry/DeviceRegistry.Autorest/examples/Get-AzDeviceRegistryNamespace.md
Show resolved
Hide resolved
|
/azp run azure-powershell - security-tools |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run azure-powershell - security-tools |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run azure-powershell - security-tools |
|
Azure Pipelines successfully started running 1 pipeline(s). |
NoriZC
approved these changes
Aug 5, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR adds support for Device Registry service's public preview api version 2025-07-01-preview version. The Asset, AssetEndpointProfile, and Billing commandlet operations are still the same and have no change, but now there are new resources to add:
Mandatory Checklist
Please choose the target release of Azure PowerShell. (⚠️ Target release is a different concept from API readiness. Please click below links for details.)
Check this box to confirm: I have read the Submitting Changes section of
CONTRIBUTING.mdand reviewed the following information:ChangeLog.mdfile(s) appropriatelysrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.## Upcoming Releaseheader in the past tense.ChangeLog.mdif no new release is required, such as fixing test case only.