# Azure Repo settings issue in 7.0 upgrade **URL:** \ **Category:** Elasticsearch\ **Created:** [April 4, 2019, 5:48pm UTC](https://discuss.elastic.co/t/azure-repo-settings-issue-in-7-0-upgrade/175456 "2019-04-04T17:48:17Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![Larry\_Wapnitsky](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/larry_wapnitsky/32/42916_2.png) [@Larry\_Wapnitsky](https://discuss.elastic.co/u/Larry_Wapnitsky)\ **Post date:** [April 4, 2019, 5:48pm UTC](https://discuss.elastic.co/t/azure-repo-settings-issue-in-7-0-upgrade/175456/1 "2019-04-04T17:48:17Z")
I'm running Elastic Stack 6.7.1 and per Kibana's `7.0 Upgrade Assistant` ( `Management` -\> `7.0 Upgrade Assistant` ), I'm being told that **Azure Repository settings have changed** , but my config files have none of the specific entries mentioned in the [documentation](https://www.elastic.co/guide/en/elasticsearch/reference/7.0/breaking-changes-7.0.html#_azure_repository_plugin). Granted, this is showing up as a warning, so I'm not sure if I can proceed or not. Advice is welcome ---
**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:** [April 4, 2019, 6:02pm UTC](https://discuss.elastic.co/t/azure-repo-settings-issue-in-7-0-upgrade/175456/2 "2019-04-04T18:02:43Z")
Could you share you settings and what the Upgrade Assistant is exactly saying? ---
**Author:** ![Larry\_Wapnitsky](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/larry_wapnitsky/32/42916_2.png) [@Larry\_Wapnitsky](https://discuss.elastic.co/u/Larry_Wapnitsky)\ **Post date:** [April 4, 2019, 6:18pm UTC](https://discuss.elastic.co/t/azure-repo-settings-issue-in-7-0-upgrade/175456/3 "2019-04-04T18:18:07Z")
This is all it provides ![image.png](https://us1.discourse-cdn.com/elastic/original/3X/b/5/b504f8e884e1a2767f64efac66aca51d17d2245f.png) ---
**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:** [April 4, 2019, 7:06pm UTC](https://discuss.elastic.co/t/azure-repo-settings-issue-in-7-0-upgrade/175456/4 "2019-04-04T19:06:04Z")
Ok. What are your settings? ---
**Author:** ![Larry\_Wapnitsky](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/larry_wapnitsky/32/42916_2.png) [@Larry\_Wapnitsky](https://discuss.elastic.co/u/Larry_Wapnitsky)\ **Post date:** [April 4, 2019, 7:29pm UTC](https://discuss.elastic.co/t/azure-repo-settings-issue-in-7-0-upgrade/175456/5 "2019-04-04T19:29:05Z")
I don't have anything in the elasticsearch.yml. Only things i've set are the key and account ---
**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:** [April 4, 2019, 7:50pm UTC](https://discuss.elastic.co/t/azure-repo-settings-issue-in-7-0-upgrade/175456/6 "2019-04-04T19:50:45Z")
How? ---
**Author:** ![Larry\_Wapnitsky](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/larry_wapnitsky/32/42916_2.png) [@Larry\_Wapnitsky](https://discuss.elastic.co/u/Larry_Wapnitsky)\ **Post date:** [April 4, 2019, 8:13pm UTC](https://discuss.elastic.co/t/azure-repo-settings-issue-in-7-0-upgrade/175456/7 "2019-04-04T20:13:19Z")
```auto bin/elasticsearch-keystore add azure.client.default.account bin/elasticsearch-keystore add azure.client.default.key ``` ---
**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:** [April 5, 2019, 1:25pm UTC](https://discuss.elastic.co/t/azure-repo-settings-issue-in-7-0-upgrade/175456/8 "2019-04-05T13:25:16Z")
Thanks. Could you open an issue in elasticsearch project? ---
**Author:** ![Larry\_Wapnitsky](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/larry_wapnitsky/32/42916_2.png) [@Larry\_Wapnitsky](https://discuss.elastic.co/u/Larry_Wapnitsky)\ **Post date:** [April 5, 2019, 1:58pm UTC](https://discuss.elastic.co/t/azure-repo-settings-issue-in-7-0-upgrade/175456/9 "2019-04-05T13:58:08Z")
will do. **Larry G. Wapnitsky** -- Join me in fighting back against cancer [http://l.wapnitsky.com/ACS](http://l.wapnitsky.com/ACS) ---
**Author:** ![Larry\_Wapnitsky](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/larry_wapnitsky/32/42916_2.png) [@Larry\_Wapnitsky](https://discuss.elastic.co/u/Larry_Wapnitsky)\ **Post date:** [April 5, 2019, 7:42pm UTC](https://discuss.elastic.co/t/azure-repo-settings-issue-in-7-0-upgrade/175456/10 "2019-04-05T19:42:18Z")
> [@Larry\_Wapnitsky](#): > > bin/elasticsearch-keystore add azure.client.default.account bin/elasticsearch-keystore add azure.client.default.key > > > Conversation started in forums \[here\](https://discuss.elastic.co/t/azure-repo-se…ttings-issue-in-7-0-upgrade/175456/2) > > I'm running Elastic Stack 6.7.1 and per Kibana's 7.0 Upgrade Assistant ( Management -\> 7.0 Upgrade Assistant ), I'm being told that Azure Repository settings have changed, but my config files have none of the specific entries mentioned in the documentation 2. Granted, this is showing up as a warning, so I'm not sure if I can proceed or not. > > !\[image\](https://user-images.githubusercontent.com/647444/55652315-27371b80-57b9-11e9-99a5-7d2a739ab14d.png) > > Nothing in config file, but have established (and successfully used) the following: > > \`\`\` > bin/elasticsearch-keystore add azure.client.default.account > bin/elasticsearch-keystore add azure.client.default.key > > \`\`\` ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [May 3, 2019, 7:42pm UTC](https://discuss.elastic.co/t/azure-repo-settings-issue-in-7-0-upgrade/175456/11 "2019-05-03T19:42:22Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.