# Azure: Normalizing Array Fields
**URL:** https://discuss.elastic.co/t/azure-normalizing-array-fields/351184
**Category:** Elastic Agent
**Tags:** integrations
**Created:** [January 16, 2024, 4:13pm UTC](https://discuss.elastic.co/t/azure-normalizing-array-fields/351184 "2024-01-16T16:13:12Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@erikg](https://discuss.elastic.co/u/erikg)
#### Post date: [January 16, 2024, 4:13pm UTC](https://discuss.elastic.co/t/azure-normalizing-array-fields/351184/1 "2024-01-16T16:13:12Z")
Hello,
I am using Elastic's Azure Integration to collect AD Audit logs. Everything is working as expected but I find the schema logic to be hard to work with.
The managed ingest pipeline runs a script to map out nested arrays in JSON. I understand why this was done. The Nested JSON has created fields like these:
`azure.auditlogs.properties.target_resources.0.display_name`
`azure.auditlogs.properties.target_resources.1.display_name`
`azure.auditlogs.properties.target_resources.2.display_name`
These are the same field but different values. Because its not under one field `azure.auditlogs.properties.target_resources.display_name ` , I am not sure how I can use these fields for visualizations.
But any advice on how to make use of this mapping structure. Perhaps there's a way I can improve on this via ingest pipeline?
Thanks
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [February 13, 2024, 4:13pm UTC](https://discuss.elastic.co/t/azure-normalizing-array-fields/351184/2 "2024-02-13T16:13:45Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.