Skip to content
anubo User Guide for anuboXBRL Reader and anuboXBRL Analyzer - Add-ins for Microsoft Excel

4. Platforms, sign-in, and Company/Microsoft 365 Administrators

4.1 Supported Microsoft Excel platforms

  • Microsoft Excel for Windows (Microsoft 365) – Full functionality

  • Microsoft Excel for Mac (Microsoft 365) – Full functionality

  • Microsoft Excel for the web – Full functionality

  • Microsoft Excel for Windows (Office LTSC 2024 / LTSC 2021) – Full functionality

  • Microsoft Excel for Windows (Office 2019, perpetual) – Supported via Credential Login. Office 2019 update must be up to date.

The listed platforms offer full functionality unless otherwise stated. For technical details about authentication methods and organizational requirements, please refer to Section 4.3.

4.2 Sign in and licensing

  • Microsoft 365 / Office LTSC 2024 / Office LTSC 2021

    • If your organization allows it, you are signed in automatically via Microsoft SSO (Single Sign-On) when you open anuboXBRL in Excel. SSO uses your Microsoft work account.
    • If you see a consent prompt, approve it (if your organization allows user consent), or ask your company administrator to grant tenant-wide consent for the add-in.
    • If you see Needs admin approval or other SSO errors, see Chapter 10 — Troubleshooting.

  • Single-user license policy

    • The anubo add-in license is a single-user license.
    • If you sign in again while already signed in — for example on a different device — the earlier session is logged out automatically.
    • You can switch between devices, but one license cannot be used on multiple devices at the same time.

  • Office 2019 (perpetual)

    • SSO is not available (Microsoft Excel builds without IdentityAPI 1.3). The add-in uses Credential Login instead.
    • Open anuboXBRL (Excel ribbon → anuboXBRL).
    • Enter the email and password you registered with.
    • After successful login, your license is validated the same way as with SSO on other platforms.
Your edition (Reader or Analyzer) appears after sign-in in the add-in (top right corner).

4.3 Company/Microsoft 365 Administrators

This section provides additional technical detail for organizational deployment and tenant configuration. For a shorter deployment walkthrough, see Section 3.4. Individual users should start with Section 3.1.

Some features — such as automatic SSO sign-in — depend on your Microsoft 365 tenant configuration. A Microsoft 365 tenant is your organization’s Microsoft cloud environment. Please review the following:

4.3.1 Microsoft 365 Admin Center (organizational deployment)

  • Open Microsoft 365 Admin Center (https://admin.microsoft.com)

  • Go to Settings → Integrated Apps

  • Click Upload custom apps

  • Select app type Office Add-in

  • Provide the manifest URL: https://prod.azan82.anubo.com/app/v1/manifests/anubo-addin-stable.xml

  • Follow the prompts to complete the installation

Note: The manifest URL may be updated to newer versions (e.g., v2) in the future. Always use the latest stable version available. The user manual is constantly updated with the latest link here. Add-in users will be notified of updates via email.

4.3.2 App permissions & consent (Microsoft Entra ID / Azure AD)

  • Open Entra ID (formerly Azure AD) → Enterprise applications and locate anuboXBRL (or search by the Application (client) ID from the add-in manifest). Entra ID is Microsoft’s identity and access management service.

  • Open Permissions (or Permissions and consent).

  • Click Grant admin consent for the required scopes: User.Read, Files.Read.All, email, openid, profile, and offline_access.

  • Confirm the status shows Granted for [Organization].

  • If your organization disables user consent, admin consent is required before first use.

  • For end-user SSO errors (for example Needs admin approval), see Chapter 10 — Troubleshooting.

4.3.3 Policies that can block SSO

  • Integrated Apps / Office Add-ins must be allowed.

  • User consent policy determines whether end users can accept the consent prompt themselves.

  • Conditional Access (MFA / device rules) can block token issuance.

  • End users must be signed into Office with their Microsoft 365 work/school account.

4.3.4 Firewall configuration requirements

To ensure reliable connectivity, allow outbound HTTPS to these domains (no inbound rules needed):

  • https://azan92.anubo.eu — Main backend API server

  • https://prod.azan82.anubo.com — Production application server

  • https://anubo.com — Company website and support

  • https://docs.anubo.com — User Guide and in-add-in help links

  • https://appsforoffice.microsoft.com — Office.js and add-in platform resources (Microsoft)

Ports

  • HTTPS (443) required

  • HTTP (80) optional, only for non-sensitive fallback requests if used by your environment (HTTPS is recommended)

Proxy / content filtering

  • Ensure no proxy rule or content filter blocks the domains above.

  • Allow long-running HTTPS requests (data processing and downloads may be larger).

  • Configure outbound HTTPS (443) to all listed domains; HTTP (80) only if your environment requires it for non-sensitive fallback traffic.

If SSO is not desired or cannot be enabled, users can always sign in via Credential Login (supported on all platforms including Office 2019).