**client secret* - the key value as created in the previous section

**tenant* -`<Your Microsoft Azure AD Domain>.onmicrosoft.com`

**Object ID* - your Azure Service Principal Object ID (from Enterprise Application configuration, see below)

**Auto Sync users and teams to Codefresh* - Select to automatically sync user accounts in Azure AD to your Codefresh account. Optionally, define the time interval, in hours, at which to sync, from 1 to 24. If you don't specify an interval, the sync is every 12 hours.

Those fields can be seen in the overview page of your application registration:

Ideally, your application should be able to access other services by other DNS names that are fully configurable (this is a very good practice for[integration tests]({{site.baseurl}}/docs/testing/integration-tests/) as well).

Sometimes, however, and especially in legacy applications, your application might be hardcoded to look at other services at`localhost`.

In that case, you can use the attribute`shared_host_network: true` on the services definition. Now all linked containers can access each other's services via localhost. Here is an example:

In that case, you can use the attribute`shared_host_network: true` on the services definition. Now all linked containers can access each other's services via localhost.

When`composition: ./docker-compose.yml` is used, this parameter is supported only in on-premises and hybrid environments. In cloud environments, for security reasons, this parameter is ignored.

Here is an example:

{% highlight yaml %}

| `tags` | Multiple tags under which to push the image. Use either this or `tag`. This is an array, so should be of the following style: <br> {::nomarkdown}<figure class="highlight"><pre><code class="language-yaml" data-lang="yaml"><span class="na">tags</span><span class="pi">:</span><br><span class="pi">-</span> <span class="s">tag1</span><br><span class="pi">-</span> <span class="s">tag2</span><br><span class="pi">-</span> <span class="s">{% raw %}${{CF_BRANCH_TAG_NORMALIZED}}{% endraw %}</span><br><span class="pi">-</span> <span class="s">tag4</span></code></pre></figure>{:/}or<br>{::nomarkdown}<figure class="highlight"><pre><code class="language-yaml" data-lang="yaml"><span class="na">tags</span><span class="pi">:</span> <span class="pi">[</span> <span class="s1">'</span><span class="s">tag1'</span><span class="pi">,</span> <span class="s1">'</span><span class="s">tag2'</span><span class="pi">,</span> <span class="s1">'</span><span class="s">{% raw %}${{CF_BRANCH_TAG_NORMALIZED}}{% endraw %}'</span><span class="pi">,</span> <span class="s1">'</span><span class="s">tag4'</span> <span class="pi">]</span></code></pre></figure>{:/} | Optional |

|`stage`| Parent group of this step. See[using stages]({{site.baseurl}}/docs/codefresh-yaml/stages/) for more information.| Optional|

|`candidate`| The identifier of the image to push to the remote Docker registry. It can be an explicit identifier of an image to push, or a variable that references a`Build` step.| Required|

|`tag`| The tag under which to push the image. Use either this or`tags`.<br> The default is`latest`.| Default|

|`region`| Relevant only for[Amazon ECR]({{site.baseurl}}/docs/integrations/docker-registries/amazon-ec2-container-registry/) integrations using either service accounts or explicit credentials. The names of the regions for which to perform cross-region replication. The names of the source region and the destination region name must be defined in separate steps.| Optional|

| `tags` | Multiple tags under which to push the image. Use either this or `tag`. This is an array, so should be of the following style: <br> {::nomarkdown}<figure class="highlight"><pre><code class="language-yaml" data-lang="yaml"><span class="na">tags</span><span class="pi">:</span><br><span class="pi">-</span> <span class="s">tag1</span><br><span class="pi">-</span> <span class="s">tag2</span><br><span class="pi">-</span> <span class="s">{% raw %}${{CF_BRANCH_TAG_NORMALIZED_LOWER_CASE}}{% endraw %}</span><br><span class="pi">-</span> <span class="s">tag4</span></code></pre></figure>{:/}or<br>{::nomarkdown}<figure class="highlight"><pre><code class="language-yaml" data-lang="yaml"><span class="na">tags</span><span class="pi">:</span> <span class="pi">[</span> <span class="s1">'</span><span class="s">tag1'</span><span class="pi">,</span> <span class="s1">'</span><span class="s">tag2'</span><span class="pi">,</span> <span class="s1">'</span><span class="s">{% raw %}${{CF_BRANCH_TAG_NORMALIZED_LOWER_CASE}}{% endraw %}'</span><span class="pi">,</span> <span class="s1">'</span><span class="s">tag4'</span> <span class="pi">]</span></code></pre></figure>{:/} | Default |

|`image_name`| The tagged image name that will be used The default value will be the same image name as of the candidate.| Default|

|`registry`| The registry logical name of one of the inserted registries from the integration view. <br>The default value will be your default registry[if you have more than one]({{site.baseurl}}/docs/docker-registries/external-docker-registries/).| Default|