# Migrating to Elastic on Azure

**URL:** <https://discuss.elastic.co/t/migrating-to-elastic-on-azure/199719>\
**Category:** Elasticsearch\
**Created:** [September 16, 2019, 7:40pm UTC](https://discuss.elastic.co/t/migrating-to-elastic-on-azure/199719 "2019-09-16T19:40:51Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![vinitp](https://avatars.discourse-cdn.com/v4/letter/v/46a35a/32.png) [@vinitp](https://discuss.elastic.co/u/vinitp)\
**Post date:** [September 16, 2019, 7:40pm UTC](https://discuss.elastic.co/t/migrating-to-elastic-on-azure/199719/1 "2019-09-16T19:40:52Z")

</div>

Hi,  
We have been using ES 6.8 (running on VM on Azure) for some time. Since ES as a Service is available on Azure, we decided to try it out. We use Spring-ElasticSearch framework to connect to the ES instance. The Previous configuration used to set with these properties:

elasticsearch.port = 9200  
elasticsearch.username=  
elasticsearch.password=

spring.data.elasticsearch.cluster-name=eml  
spring.data.elasticsearch.cluster-nodes=ip-address:9300  
elasticsearch.host = ip-address  
elasticsearch.clustername = eml

I changed it to the following after setting up an instance as service:  
elasticsearch.port = 9243  
elasticsearch.username=elastic  
elasticsearch.password=myPassword

spring.data.elasticsearch.cluster-name = 18530cecb11645779c62ac9df64937d2  
[spring.data.elasticsearch.cluster-nodes:9243=18530cecb11645779c62ac9df64937d2.eastus2.azure.elastic-cloud.com](http://spring.data.elasticsearch.cluster-nodes:9243=18530cecb11645779c62ac9df64937d2.eastus2.azure.elastic-cloud.com)  
elasticsearch.host = [18530cecb11645779c62ac9df64937d2.eastus2.azure.elastic-cloud.com](http://18530cecb11645779c62ac9df64937d2.eastus2.azure.elastic-cloud.com)  
elasticsearch.clustername = 18530cecb11645779c62ac9df64937d2

However, I get the following error when I start the service:  
**"failed to load elasticsearch nodes : org.elasticsearch.client.transport.NoNodeAvailableException: None of the configured nodes are available: [{#transport#-1}{uYK45RfYSpWJ9iMu6MTx-Q}{[18530cecb11645779c62ac9df64937d2.eastus2.azure.elastic-cloud.com](http://18530cecb11645779c62ac9df64937d2.eastus2.azure.elastic-cloud.com)}{20.190.254.196:9243}]"**

Is something wrong with my configuration? Though, I was able to connect to the ES and Kibana without any problem.

---

<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:** [October 14, 2019, 7:41pm UTC](https://discuss.elastic.co/t/migrating-to-elastic-on-azure/199719/2 "2019-10-14T19:41:09Z")

</div>

Closed on October 14, 2019, 7:41pm UTC

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