The existing Azure DevOps integration does not support ingesting data about iterations (though the iteration path itself does come in as an attribute of a work item). Having the iterations themselves coming through as a "kind" (using the data from this endpoint) would allow us to further refine our "my work" entity table to allow users to focus specifically on work items in the current iteration (or view different iterations in the past/future) more easily, as we could compare the start/end date of a given iteration to the current date (much like ADO allows users to do today in their sprint view).