# Azure Signin data =\> field \[message\] already exists

**URL:** <https://discuss.elastic.co/t/azure-signin-data-field-message-already-exists/278446>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [July 12, 2021, 4:38pm UTC](https://discuss.elastic.co/t/azure-signin-data-field-message-already-exists/278446 "2021-07-12T16:38:17Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![willemdh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/willemdh/32/16922_2.png) [@willemdh](https://discuss.elastic.co/u/willemdh)\
**Post date:** [July 12, 2021, 4:38pm UTC](https://discuss.elastic.co/t/azure-signin-data-field-message-already-exists/278446/1 "2021-07-12T16:38:17Z")

</div>

Hello,

I've seen multiple occurences in the Azure signin logs where `user.name` was not populated. Those documents always have an `error.message` containing `"field [message] already exists"`.

This seem like a bug.. The message field in those documents apparently has the same value as the filed `azure.signinlogs.result_description`, for example `"Users' needs to enroll for second factor authentication (interactive)."`

Sounds like a bug in the pipeline to me, ok if I make a GH issue?

Best regards,

Willem

---

<div class="post-metadata">

**Author:** ![legoguy1000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/legoguy1000/32/54301_2.png) [@legoguy1000](https://discuss.elastic.co/u/legoguy1000)\
**Post date:** [July 13, 2021, 2:56am UTC](https://discuss.elastic.co/t/azure-signin-data-field-message-already-exists/278446/2 "2021-07-13T02:56:01Z")

</div>

It's because of this, [beats/pipeline.yml at 11b545a182909de2234aed8bf2916f16f2234f5e · elastic/beats · GitHub](https://github.com/elastic/beats/blob/11b545a182909de2234aed8bf2916f16f2234f5e/x-pack/filebeat/module/azure/signinlogs/ingest/pipeline.yml#L238). definitely needs to be modified. Create the issue and I can fix it.

---

<div class="post-metadata">

**Author:** ![legoguy1000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/legoguy1000/32/54301_2.png) [@legoguy1000](https://discuss.elastic.co/u/legoguy1000)\
**Post date:** [July 13, 2021, 3:21am UTC](https://discuss.elastic.co/t/azure-signin-data-field-message-already-exists/278446/3 "2021-07-13T03:21:12Z")

</div>

When u create the GitHub issue, can u share the sample log that was being parsed that caused the issue so I can test the fix actions.

---

<div class="post-metadata">

**Author:** ![willemdh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/willemdh/32/16922_2.png) [@willemdh](https://discuss.elastic.co/u/willemdh)\
**Post date:** [August 4, 2021, 8:06pm UTC](https://discuss.elastic.co/t/azure-signin-data-field-message-already-exists/278446/4 "2021-08-04T20:06:28Z")

</div>

> <https://github.com/elastic/beats/issues/27240>
>
> \- Version: 7.13.1
> \- Operating System: Centos 8
> \- Discuss Forum URL: https://di…scuss.elastic.co/t/azure-signin-data-field-message-already-exists/278446
> 
> Issue in https://github.com/elastic/beats/blob/11b545a182909de2234aed8bf2916f16f2234f5e/x-pack/filebeat/module/azure/signinlogs/ingest/pipeline.yml#L238
> 
> I cannot provide any sample logs for now. Maybe later @legoguy1000

Thanks!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [September 1, 2021, 10:07pm UTC](https://discuss.elastic.co/t/azure-signin-data-field-message-already-exists/278446/5 "2021-09-01T22:07:27Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.