microsoftgraph / microsoftgraph/dataconnect-solutions
Question - Best approach to get attributes not available in the standard datasets
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 72
- Forks
- 52
- PR merge metrics
- No merged PRs in 30d
Description
We are using the Graph Data Connect to extract Azure AD information for all users in our tenant (using Azure Data Factory). The extractions works as expected but there are fields that don't seem to be available in the standard schemas (e.g. Employee ID or schema extensions).
What's the best approach to get these fields? Should we then use the API to get these values for each user?
Is there a better, more efficient, approach?
Thanks!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the Graph Data Connect standard schemas and the Azure Data Factory extraction described in the issue, then compare them with the API approach for per-user values. Done would be a documented, supported approach for retrieving Employee ID and schema extensions, including whether a more efficient alternative exists.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, data-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100