Record the Defender for Identity workspace ID and name for support and proxy changes

Use this document to connect an official requirement or behavior to observable evidence: Record the Defender for Identity workspace ID and name for support and proxy changes. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official View information on the Defender for Identity About page from Microsoft supports the following bounded statements:

• The Defender for Identity About page reports the workspace ID and name, latest available sensor version, assigned license count, and identities active during the preceding 28 days. The research record locates this support at Information shown on the Defender for Identity About page > details list.
• Microsoft directs administrators to use the About-page identifiers for troubleshooting or support and to supply the workspace name when setting proxy or firewall connectivity. The research record locates this support at Information shown on the Defender for Identity About page > paragraph following the details list.

The source support ends with the statements listed above. Use them to examine Defender for Identity workspaces, sensors, directory-service accounts, action accounts, network paths, roles, and deployment health in the applicable environment, not to imply a wider guarantee.

What the source does not establish

Workspace identifiers support inventory and escalation; they do not prove sensor connectivity, health, license entitlement, data ingestion, or support-case resolution. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine Active Directory, Windows DNS, time, certificates, domain-controller resources, network capture, cloud connectivity, and security operations before translating the source into an operational decision.

Applicability questions

• For source statement 1 at Information shown on the Defender for Identity About page > details list, which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at Information shown on the Defender for Identity About page > paragraph following the details list, which observable configuration, record, or test can confirm applicability here?
• Which deployed instance of Defender for Identity workspaces, sensors, directory-service accounts, action accounts, network paths, roles, and deployment health will be compared with the source, and why that instance?
• How will the review distinguish a source mismatch from a failure in Active Directory, Windows DNS, time, certificates, domain-controller resources, network capture, cloud connectivity, and security operations?
• Who approves the conclusion, exception, test window, and rollback threshold?

DSE recommendation:

DSE recommends using the cited source as the evidence anchor for this decision. Make the source, asset scope, owner, and expected outcome explicit in the review record. Record the source location, examined part of Defender for Identity workspaces, sensors, directory-service accounts, action accounts, network paths, roles, and deployment health, observed and expected states, owner, and reason for deviation.

For an approved change, define prerequisites, a limited test path, success and stop conditions, monitoring, and rollback. Check Active Directory, Windows DNS, time, certificates, domain-controller resources, network capture, cloud connectivity, and security operations in design order. Protect credentials, keys, recovery material, personal data, and sensitive topology in evidence.

Verification and evidence

Evidence should let another reviewer reproduce this decision. Retain observations beside the traced locations Information shown on the Defender for Identity About page > details list; Information shown on the Defender for Identity About page > paragraph following the details list. Favor sensor inventory, service and action-account permissions, health alerts, connectivity tests, portal state, and controlled detection tests, linked to stable identifiers, time, and operator.

Keep before-state evidence, approval, test or change result, exceptions, and after-state evidence together. Use an approved lab, window, or nonproduction path for risky tests. Set a recheck trigger for version, architecture, dependency, vendor, incident, or ownership change. A check proves only what was observed.

Official references

• View information on the Defender for Identity About page — Microsoft