Azure discovery issues
Duplicate Azure devices in vScope
Section titled “Duplicate Azure devices in vScope”- Toggle: Discovery Manager → Credentials → AzureRM → Merge duplicate devices.
- Effect: vScope groups devices with the same hardware ID and shows only the newest; Azure/Entra is untouched.
- When to use: You see duplicate devices caused by enrollment noise and don’t want to clean them in Azure.
- Related: Troubleshooting: Duplicates and Stale Objects in Microsoft Entra ID.
Match local and Azure domains
Section titled “Match local and Azure domains”Azure often uses a different domain than on-prem AD. Align them so assets merge correctly.
Steps:
- In vScope, go to Discovery → Suggestions.
- Create a Custom suggestion to map equivalent domains (e.g.,
vscope.net↔company.com). - Apply and rerun discovery.
M365 license friendly names look odd
Section titled “M365 license friendly names look odd”- vScope shows Microsoft’s published “Friendly Name” values.
- Microsoft frequently renames plans; casing and naming may lag their Admin Center.
- We periodically refresh these names; discrepancies often resolve when Microsoft updates their feed.
Common errors
Section titled “Common errors”| Error | What happened | Suggested action |
|---|---|---|
| Failed to retrieve… | Azure API call failed. | Confirm the app has all required API permissions and admin consent. |
| SSLHandshakeException | TLS handshake failed. | Verify network path and certificates between vScope and Azure. |
| java.lang.RunTimeException: Found Duplicate ID’s | Microsoft Graph returned duplicate identifiers. | Usually temporary; retry after a short interval. |