Press CTRL+K to open search

Publish online

  • 2 minute(s) read
Prev Next

Overview

Publish online lets you publish a generated Azure technical document directly to Document360, a knowledge-base platform, instead of distributing it manually through file shares or email.

Business value

Publishing straight to a knowledge base removes the manual work of distributing documents through file shares, email, or shared folders. Teams get a centralized, always-current home for generated documentation that their audience can access directly.

Prerequisites

  • A Document360 account. See Document360's own account creation guide for details.
  • A new project in Document360, along with an API token, to connect Turbo360 Cloud Docs with Document360.

For a seamless setup, sign up to Document360 using the same email address used for your Turbo360 account.

  • If the Turbo360 and Document360 accounts use different emails, add the Turbo360 account's user as a team member in Document360.
  • If the Turbo360 account uses Active Directory sign-in, add the contact email provided in Turbo360 as a user in Document360.

See Document360's guide on adding team members for details.

Note the correct project name and API token from Document360 carefully.

Confirm the Document360 account connected to Cloud Docs has its site access visibility set to Private. See Document360's guide on making a knowledge base private for details.

Steps

Use the following steps to publish a generated document to Document360. Go to Publish settings when generating a document to get started.

  1. Select Publish document to Document360 in the Publish settings section.
  2. Provide the Document360 Project Name and its API Token to associate the Document360 project with the document configuration.

For further reference, see Document360's guides on creating a project and generating an API token.

Example scenario

A team wants their generated Resource details documents to be immediately accessible to internal stakeholders without manual distribution. They create a private Document360 project, generate an API token, then select Publish document to Document360 in Publish settings and provide the project name and token.

Limitations

Publishing to Document360 requires an active Document360 account, project, and API token — it cannot be configured without them. If the Document360 project isn't set to private visibility, published content may be more widely accessible than intended.

Troubleshooting

  1. Document isn't published to Document360 after configuring Publish settings
    Cause: the Project Name or API Token entered may be incorrect.
    Fix: confirm both values match exactly what's shown in the Document360 project settings.

  2. A user added to Turbo360 can't access the connected Document360 project
    Cause: the Turbo360 and Document360 accounts may use different email addresses, and the user hasn't been added as a Document360 team member.
    Fix: add the user as a team member in Document360, or use matching email addresses across both accounts.

  3. Published content is more widely visible than expected
    Cause: the Document360 project's site access visibility may not be set to Private.
    Fix: set the connected Document360 account's site access visibility to Private.

FAQs

  1. What do I need before I can publish a document online?
    A Document360 account, a project within it, and an API token to connect that project to the document configuration.

  2. Does my Turbo360 and Document360 account need to use the same email?
    It's recommended for a seamless setup, but not required — if they differ, add the Turbo360 account's user as a team member in Document360 instead.

Related articles