# Azure ARM Discovery Plugin missing

**URL:** <https://discuss.elastic.co/t/azure-arm-discovery-plugin-missing/108138>\
**Category:** Elasticsearch\
**Created:** [November 17, 2017, 1:27pm UTC](https://discuss.elastic.co/t/azure-arm-discovery-plugin-missing/108138 "2017-11-17T13:27:37Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Itamar\_Syn\_Hershko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/itamar_syn_hershko/32/725_2.png) [@Itamar\_Syn\_Hershko](https://discuss.elastic.co/u/Itamar_Syn_Hershko)\
**Post date:** [November 17, 2017, 1:27pm UTC](https://discuss.elastic.co/t/azure-arm-discovery-plugin-missing/108138/1 "2017-11-17T13:27:37Z")

</div>

The docs in the Azure discovery plugin part say it's deprecated since 5.0,0 and "Use coming Azure ARM Discovery plugin instead" (see [https://www.elastic.co/guide/en/elasticsearch/plugins/6.0/discovery-azure-classic.html](https://www.elastic.co/guide/en/elasticsearch/plugins/6.0/discovery-azure-classic.html)), However no such ARM plugin exists.

Are there plans to lunch it? any ETA on that?

In the meantime, what is the official advise for discovery on Azure - using the "Classic" plugin? Multicast? or ..?

Thanks

---

<div class="post-metadata">

**Author:** ![rjernst](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rjernst/32/6363_2.png) [@rjernst](https://discuss.elastic.co/u/rjernst)\
**Post date:** [November 17, 2017, 5:16pm UTC](https://discuss.elastic.co/t/azure-arm-discovery-plugin-missing/108138/2 "2017-11-17T17:16:50Z")

</div>

I believe the PR is stalled on figuring out some security manager issues:

> <https://github.com/elastic/elasticsearch/pull/22679>

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [November 17, 2017, 5:35pm UTC](https://discuss.elastic.co/t/azure-arm-discovery-plugin-missing/108138/3 "2017-11-17T17:35:12Z")

</div>

Yes it is.

I started to look at it again today to see if the latest Azure SDK version solves the security manager issues.  
If it does not, I'll probably need some help on this.

But the best thing to do is to "watch" the PR.

---

<div class="post-metadata">

**Author:** ![Itamar\_Syn\_Hershko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/itamar_syn_hershko/32/725_2.png) [@Itamar\_Syn\_Hershko](https://discuss.elastic.co/u/Itamar_Syn_Hershko)\
**Post date:** [November 19, 2017, 1:44pm UTC](https://discuss.elastic.co/t/azure-arm-discovery-plugin-missing/108138/4 "2017-11-19T13:44:42Z")

</div>

> In the meantime, what is the official advise for discovery on Azure - using the "Classic" plugin? Multicast? or ..?

What is the official advice to set up discovery on Azure then?

If all the above are discouraged, is there an ETA to have this ready for general use?

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [November 19, 2017, 2:05pm UTC](https://discuss.elastic.co/t/azure-arm-discovery-plugin-missing/108138/5 "2017-11-19T14:05:30Z")

</div>

IMHO I'd prefer first using unicast as IIRC azure IP addresses are not moving.  
Then, I'd use the azure old plugin.

---

<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:** [December 17, 2017, 2:05pm UTC](https://discuss.elastic.co/t/azure-arm-discovery-plugin-missing/108138/6 "2017-12-17T14:05:37Z")

</div>

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