Overview

Rogue’s SharePoint integration allows your organization to seamlessly access and utilize documents stored in Microsoft SharePoint directly within the Rogue platform. This integration enables you to:

  • Access SharePoint files without leaving Rogue
  • Search across both Rogue and SharePoint content simultaneously
  • Use SharePoint documents in your War Rooms and document generation
  • Maintain secure, read-only access to your SharePoint content

Benefits

Centralized Access

Access all your organization’s documents from one place without switching between platforms

Enhanced Search

Search across both Rogue’s Data Shelf and SharePoint libraries simultaneously

Secure Integration

Read-only access ensures your SharePoint content remains protected

Easy Setup

One-time configuration that takes less than 15 minutes

Prerequisites

Before setting up the SharePoint integration, ensure you have:

  • Administrator access to your organization’s Azure portal
  • Permission to create and manage app registrations in Azure
  • Access to your Rogue organization’s settings

Setup Instructions

Step 1: Register Application in Azure Portal

  1. Navigate to the Azure Portal (or Azure US Government for government organizations)

  2. Register a new application:

    • Go to Microsoft Entra ID (formerly Azure Active Directory)
    • Select App registrationsNew registration
    • Name the application: Rogue SharePoint Integration
    • Select the appropriate account type for your organization
    • Click Register

Depending on your Azure dashboard setup, the app registration feature may be located under Microsoft Entra ID instead of the traditional Azure AD location.

Step 2: Configure API Permissions

  1. From your new application’s overview page, navigate to: ManageAPI PermissionsAdd a permission

  2. Select Microsoft GraphApplication permissions

  3. Grant the following permissions:

    • Files.Read.All - Read files in all site collections
    • Sites.Read.All - Read items in all site collections
  4. Click Add permissions

  5. Important: Have an administrator click Grant admin consent for these permissions

Administrator consent is required for the integration to function. Without this step, Rogue will not be able to access your SharePoint files.

Step 3: Create Client Secret

  1. Navigate to: ManageCertificates & secretsClient secretsNew client secret

  2. Configure the secret:

    • Description: Rogue Access (or another recognizable name)
    • Expiration: Choose a duration that aligns with your security policies
    • Click Add
  3. Important: Copy the secret value immediately after creation. You won’t be able to view it again.

You can revoke this secret at any time through the Azure portal if needed. Consider setting a reminder to rotate the secret before it expires.

Step 4: Configure Integration in Rogue

  1. In your Rogue dashboard, navigate to: SettingsManage Integrations

  2. Select SharePoint Integration

  3. Provide the following information:

    • Application (Client) ID: Found on your app’s overview page in Azure
    • Client Secret: The value you copied in Step 3 (not the ID)
    • Tenant ID: Found on your app’s overview page in Azure
    • Azure Cloud:
      • Select “Commercial” if you created your app on portal.azure.com
      • Select “US Government” if you created your app on portal.azure.us
  4. Click Connect to complete the integration

Using SharePoint in Rogue

Once configured, your SharePoint documents will be accessible throughout Rogue:

In War Rooms

  • SharePoint files appear alongside Data Shelf documents
  • Use the filter options to view only SharePoint content
  • Documents are automatically indexed for AI-powered search

In Document Generation

  • Reference SharePoint documents when creating new content
  • Pull information from SharePoint files into your responses
  • Maintain consistency with existing organizational content
  • Global search includes SharePoint results
  • Filter results by source (Data Shelf vs SharePoint)
  • Preview SharePoint documents directly in Rogue

Security Considerations

  • Read-Only Access: The integration provides read-only access to prevent accidental modifications
  • Scoped Permissions: Only the specific permissions required for functionality are requested
  • Revocable Access: You can revoke access at any time through Azure portal
  • Audit Trail: All access is logged in both Azure and Rogue for compliance

Troubleshooting

Support

If you encounter issues during setup or usage:

  1. Review the setup steps to ensure all were completed correctly
  2. Check the troubleshooting section above
  3. Contact Rogue support at success@userogue.com with:
    • Your organization name
    • Step where the issue occurred
    • Any error messages received