Frequently Ask Questions
Have a look at this page
Yes, Microsoft Account and Azure Active Directory account are supported. Note that B2B Connector is not supported yet
There is no specific requirement for this scenario. You just need to have an account (wether a Microsoft Account or an Azure Active Directory) that has the appropriate permissions to the customer subscription.
- To document ARM Resources, you don't need to have administrator privileges : Permissions applied to Azure Resources will automatically be taken into account by CloudocKit . For instance if you generate documentation for a subscription with 10 Virtual Machines and you have access to only one (even in read only), only this Virtual Machine will be documented
- To document Classic Resources, you need to be co-admin has Classic does not offer RBAC (Role Based Access Control)
- To document Azure Active Directory, you need to be Azure Active Directory Global Administrator. Note that is not a requirement : you choose that when Signing into CloudocKit t
- You can refer to this page to have more details
- Yes, just go to Cloudockit Generation Portal and Sign In. It will detect that you have no license and it will automatically bring you to the Trial Mode. Note that some content will be removed as you are in Trial
- You can also check our example documentation
- In the options, there is a tab Advanced Settings that you need to use
- Navigate to this tab and enter your storage account name (will be used to store snapshots) and select a document to compare to
- Refer to the Options page of this help to have all the details on how to setup that
- Yes. Refer to our Pricing Page for more details.
- Please refer to Needs Admin Approval for more details.
- You can schedule the document generation so that you don't have to log every time.
- Refer our Pricing Page for more details.
- Cloudockit allows you to create your own template
- Refer to this page to have all the detailed step on how to customize the template
- Yes, we do offer a Windows application that does that.
- By using this application, everything will be done in your environments.
- During the document generation, CloudocKit ocKit never has access to the credentials you are using to Sign In as you are redirected to Microsoft Login Page
- The document is generated in memory in an isolated process and nothing get stored on disk.
- When the document generation is done, by default, it is stored in a blob storage with a specific key that only you will have. This is the default behavior and we also support uploading the document in your Azure Blob Storage or in a Office 365 Document Library. In that case, we will not keep anything
- CloudocKit supports this scenario.
- The first step is to Sign In into CloudocKit using the account that is licensed (even if this account has not privileges on the subscription to document).
- Once Logged In, select Azure and a popup window will allows you to change user.
- Cloudockit can scan your Hyper-V and VMware hosts to generate a complete documentation of your environments. Please refer to here for more details.
- Cloudockit gives your multiple options to schedule your document generation. Please refer to here for more details.