Troubleshooting

Troubleshooting

Before starting any troubleshooting, you need to logout from the Azure management portals (https://manage.windowsazure.com and https://portal.azure.com) and go back to Azure DocKit in private mode. Indeed, most of the issues are due to the fact that wrong credentials are used when trying to Sign In into Azure DocKit.

  • The first question being asked is the tenant name. What should I enter in this?

  • When I try to log in to Azure DocKit, I get the error AADTSTS900093 : Does not have access to consent

    • This means that the Azure Active Directory Global Administrator has explicitely prevented users to use 3rd Party Application.
    • You can confirm that by going in the Azure Active Directory Blade (on portal.azure.com), and then select User Settings. If Users can allows apps to access their data is set to No, it means that the Azure Active Directory Global Administrator has explicitely prevented users to use 3rd Party Application.
    • You have two options : Change this settings to allow users to use Azure DocKit or Ask an Azure Global Administrator to generate the documentation using Azure DocKit

  • When I Sign In into Azure DocKit, the list of subscriptions is emtpy.

    • If you do not see any subscription in the drop down list, it means that you do not have access to any subscription. To ensure that you have access to at least one subscription, you can connect to https://manage.windowsazure.com and https://portal.azure.com. If you do not see any subscription in those 2 portals it means that you have not the required access.

  • When I click on a generated document, I get a message telling that the token is expired.

    • For security reasons, the secured link that you receive automatically expire after a certain period of time. So you will need to regenerate the document. You can change this amount of time if you want (using the Drop Off Tab)

  • When I Sign In into Azure DocKit, I get an error message saying Calling principal cannot consent due to lack of permissions.

    • You must have checked the checkbox specifying that you are an Azure Active Directory Global Admin. This requires that you are Azure AD Global Admin which is not the case. Restart the process without checking the checkbox.

  • When I Sign In into Azure DocKit, I get an error message AADSTS90002: Requested tenant identifier '00000000-0000-0000-0000-000000000000' is not valid. Tenant identifiers may not be an empty GUID.

    • This is due to an issue with Azure Active Directory and specific Microsoft accounts.
    • Please use an account that is a member of the Azure Active Directory, not a Microsoft Account.

  • I cannot see the Classic Azure Component (ASM, not ARM) (like Classic Virtual Machine) in the document that is generated but I can see them in the portal.

    • For ARM component, Azure DocKit supports the role like reader or contributor but for Classic Deployment model, you need to be Administrator of the subscription (specified in the https://manage.windowsazure.com portal).

  • The document I get is empty. There may be multiple reasons why the document is empty. Please check the following elements:

    • When you are logged into https://generate.azuredockit.com open a new tab and navigate to https://portal.azure.com. You should see some resources. If you only see the active directory and not other resources, it means that the document will not contain anything.
    • Filters that you have applied may be to restrictive. Please remove them.
    • If you have used a custom template, please use with the built-in template to ensure that the issue is not due to the template.

  • I have specified a Storage Account to drop the document but I cannot see the document even if the generation is successful.

    • You need to ensure that the account you are using has write permissions to the storage

  • I have a G2-U or G2-T license but the user that is licensed do not have appropriate permissions on the subscription that I need to document. I need to use another account.
    • Azure DocKit supports this scenario.
    • The first step is to Sign In into Azure DocKit using the account that is licensed (even if this account has not privileges on the subscription to document).
    • Once Logged In, you will see a button on the top of the windows that allows you to change user. Click on that and then you need to enter the account that you want to use.
    • Once done, click on Log Out.
    • Now, go back to the Azure DocKit home page and Sign In with this account.
    • You should now have a valid license.
    • Note that you have 5 minutes to do that
    • Note that it is not legal to use this mechanism to give a license to someone else