Skip to content

Windows agent enrollment: populate the IdP host vitals automatically for Entra-joined devices #50145

Description

@melpike

Goal

User story
As an IT admin,
I want Fleet to populate IdP host vitals automatically for Entra-joined devices
so that I don't have to do any additional authentication.

Changes

Product

  • UI changes: TODO
  • CLI (fleetctl) usage changes: TODO
  • YAML changes: TODO
  • REST API changes: TODO
  • Fleet's agent (fleetd) changes: TODO
  • Fleet server configuration changes: TODO
  • Exposed, public API endpoint changes: TODO
  • fleetdm.com changes: TODO
  • GitOps mode UI changes: TODO
  • GitOps generation changes: TODO
  • Activity changes: TODO
  • Permissions changes: TODO
  • Changes to paid features or tiers: TODO
  • My device and fleetdm.com/better changes: TODO
  • Usage statistics: TODO
  • Other reference documentation changes: TODO
  • First draft of test plan added
  • Once shipped, requester has been notified
  • Once shipped, dogfooding issue has been filed

Engineering

  • Test plan is finalized
  • Contributor API changes: TODO
  • Feature guide changes: TODO
  • Database schema migrations: TODO
  • Load testing: TODO
  • Pre-QA load test: TODO
  • Load testing/osquery-perf improvements: TODO

ℹ️  Please read this issue carefully and understand it. Pay special attention to UI wireframes, especially "dev notes".

Risk assessment

  • Requires testing in a hosted environment: TODO
  • Requires load testing: TODO
  • Risk level: Low / High TODO
  • Risk description: TODO

Test plan

Make sure to go through the list and consider all events that might be related to this story, so we catch edge cases earlier.

Core flow

  • TODO

Edge cases

  • TODO

Supplemental testing

Testing notes

Confirmation

  1. Engineer: Added comment to user story confirming successful completion of test plan (include any special setup, test data, or configuration used during development/testing if applicable).
  2. QA: Added comment to user story confirming successful completion of test plan.
  3. QA: Determined whether this story needs Playwright automation.
    • Needs automation: Yes / No
    • If yes, filed a follow-up issue in the :help-qa project with status "Needs automation":

Metadata

Metadata

Assignees

Labels

#g-power-to-pcPower to the PC working groupcustomer-cisneros-wstoryA user story defining an entire feature~product-maturityContributes to Fleet's product maturity goals for the current year~windows-workstationProduct maturity category

Type

No type

Projects

Status
No status
Status
🪿 Drafting

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions