How to extract endpoint data from SD-A for use in Active Directory?

[HansK_NL]

In traditional networks a subnet has (usually) a 1:1 association with a location. In desktop management systems (such as Microsoft SCCM) these subnet based "boundaries" are used to perform client management tasks.

Using SD-A a subnet is now a fabric wide entity and as such, the IP address of an endpoint no longer holds a relation to the location of an endpoint. In other words: IP subnet based boundaries in SCCM must be replaced by some other boundary definition.

Within SD-A, this location information is readily available (in DNAC itself, or ISE). So, what is the best strategy to extract relevant endpoint data from either system and import this data into Active Directory or SCCM or...?

• API Calls (scheduled or triggered)?
• Reports?
• etc

Any ideas?

[Andrii Oliinyk]

hi

i'm not sure about your most granular experience of MS SCCM boundary definition, but if it's subnet then unlikely something is to be changed. i dont see anything preventing u from working with DNA's sites & its designated subnets which quite good correspond to MS SCCM boundary combinations of IP-subnet/Site/VPN. 
Being sceptic about frequent requests to ISE/DNAC via API to update your SCCM to be pragmatic enough i'd say the reporting from DNAC could be your friend for nonfrequent updates.