Skip to main content
DocuSignCustomer feedback

A customer notes that switching from DocuSign is not realistic due to external signer expectations, despite integration issues with Microsoft Purview encryption on signed PDF/A outputs.

What happened

Post: "Purview sensitivity labels with encryption won’t apply to signed PDF/A files from DocuSign. How are you handling this?"

Source

Post

Highlighted: the lines this signal was extracted from

We’re rolling out Microsoft Purview sensitivity labels with encryption. Standard PDFs label without issue. The problem is PDFs that come back digitally signed from DocuSign. The completed files are PDF/A (archival format), and Purview won’t apply the label to them. This may be working as designed, since the PDF/A standard prohibits encryption. What we’ve looked at so far: Vendor cloud conversion: One PDF vendor offered an API-based workaround that uploads each document to their cloud for conversion and sends it back. That means sending sensitive files to a third party and loosening DLP egress rules to allow it. Not an option for us. Desktop PDF tools: We’re testing whether Adobe Acrobat or Foxit handle signed PDF/A files differently on the desktop. (Do you have suggestions for others?) Switching e-sign platforms: Not realistic, since external signers expect DocuSign. Our understanding is that any platform applying a digital signature would produce the same result. It would be an impossibly hard lift to switch from DocuSign. Questions: Do you use Microsoft Purview to label and encrypt your data? If so, have you hit this with signed or PDF/A files? How did you handle it: labeling before signing, a setting in your e-sign platform, a different protection method, or a documented exception? Side question: what PDF viewer/editor does your org standardize on? This isn’t...

Keep reading with a free account

The rest of this post, and every signal for DocuSign, is in your free account.

Comments on the post

  • “I wish I had an answer for you, but I am in the same situation and looking for answers.”

    u/thejohncarlson1 points · Oct 10, 2026View

  • “This looks like a product limitation rather than a missing toggle. Microsoft’s SharePoint/OneDrive labeling docs explicitly say signed PDFs are not supported, and its Office labeling docs say PDF/A cannot be used with a label that applies encryption. I would keep the completed DocuSign PDF/A as the signed archival original, document an exception for that file type, and protect access at the reposi”

    u/graliusakaspeed1 points · Oct 11, 2026View

Extracted by Autobound

From the Signal API record
Signal
Customer feedback

What this signalsUser posts often show product pain before it reaches reviews or churn.

Subreddit
r/Office365
Event date
Oct 2026

Companies

  • MicrosoftAlso named

The full record

From the Signal API record

Numbers

Mentions
2

Details

Timing
Ongoing state
Category
Integration
Virality
Very low
Post kind
Text
Prominence
Core
Company's role
Vendor

Topics and mentions

Topics

  • esignature
  • integration
  • pdf

Extraction

Sentiment
Neutral
Detected
Oct 9, 2026
signal_type
reddit-company
signal_subtype
customerFeedback

Use this data

Get every Reddit signal for DocuSign and the companies you sell to, in the tools you already use.

  1. Ask Claude about it

    Connect Autobound to Claude, Claude Code or Cursor with MCP. Then ask: “What changed at DocuSign this week?”

  2. Send it to your own tools

    The Signal API returns Reddit signals for any list of companies as JSON, for your CRM, warehouse or app.

  3. Try it free

    Sign up and spend your free credits on the companies you sell to.

    Start Free1,000 free credits

The API returns more than this page shows

This page shows a preview. The full reddit-company record in the Signal API and MCP can also have these 8 fields. Some fields are empty for some signals.

Company

  • linkedin_urlValue in the API
  • industriesValue in the API
  • employee_count_lowValue in the API
  • employee_count_highValue in the API
  • revenueValue in the API
  • descriptionValue in the API

Signal

  • signal_nameValue in the API
  • associationValue in the API
Show the full JSONThe record on this page and the API request

GET /v1/signals/94393ea1-6b21-58cd-a78e-3e737eba361a returns this record as JSON. POST /v1/companies/enrich returns every signal for docusign.com.

{
  "signal_id": "94393ea1-6b21-58cd-a78e-3e737eba361a",
  "signal_type": "reddit-company",
  "signal_subtype": "customerFeedback",
  "detected_at": "2026-10-09T20:24:29+00:00",
  "company": {
    "name": "DocuSign",
    "domain": "docusign.com"
  },
  "data": {
    "nsfw": false,
    "stage": "none",
    "awards": 0,
    "timing": "ongoing_state",
    "topics": [
      "esignature",
      "integration",
      "pdf"
    ],
    "post_id": "1x1w02l",
    "summary": "A customer notes that switching from DocuSign is not realistic due to external signer expectations, despite integration issues with Microsoft Purview encryption on signed PDF/A outputs.",
    "category": "integration",
    "comments": [
      {
        "url": "https://www.reddit.com/r/Office365/comments/1x1w02l/comment/pf3mjn6/",
        "depth": 0,
        "score": 1,
        "author": "thejohncarlson",
        "excerpt": "I wish I had an answer for you, but I am in the same situation and looking for answers.",
        "posted_at": "2026-10-10T19:02:43.000Z",
        "author_url": "https://www.reddit.com/user/thejohncarlson/"
      },
      {
        "url": "https://www.reddit.com/r/Office365/comments/1x1w02l/comment/pf7tp7v/",
        "depth": 0,
        "score": 1,
        "author": "graliusakaspeed",
        "excerpt": "This looks like a product limitation rather than a missing toggle. Microsoft’s SharePoint/OneDrive labeling docs explicitly say signed PDFs are not supported, and its Office labeling docs say PDF/A cannot be used with a label that applies encryption. I would keep the completed DocuSign PDF/A as the signed archival original, document an exception for that file type, and protect access at the reposi",
        "posted_at": "2026-10-11T10:31:18.000Z",
        "author_url": "https://www.reddit.com/user/graliusakaspeed/"
      }
    ],
    "evidence": [
      "[post] The problem is PDFs that come back digitally signed from DocuSign. The completed files are PDF/A (archival format), and Purview won’t apply the label to them.",
      "[post] Switching e-sign platforms: Not realistic, since external signers expect DocuSign. Our understanding is that any platform applying a digital signature would produce the same result. It would be an impossibly hard lift to switch from DocuSign."
    ],
    "virality": "very_low",
    "post_date": "2026-10-09T20:24:29.000Z",
    "post_kind": "text",
    "post_text": "We’re rolling out Microsoft Purview sensitivity labels with encryption. Standard PDFs label without issue. The problem is PDFs that come back digitally signed from DocuSign. The completed files are PDF/A (archival format), and Purview won’t apply the label to them.\n\nThis may be working as designed, since the PDF/A standard prohibits encryption.\n\nWhat we’ve looked at so far:\n\nVendor cloud conversion: One PDF vendor offered an API-based workaround that uploads each document to their cloud for conversion and sends it back. That means sending sensitive files to a third party and loosening DLP egress rules to allow it. Not an option for us.\n\nDesktop PDF tools: We’re testing whether Adobe Acrobat or Foxit handle signed PDF/A files differently on the desktop. (Do you have suggestions for others?)\n\nSwitching e-sign platforms: Not realistic, since external signers expect DocuSign. Our understanding is that any platform applying a digital signature would produce the same result. It would be an impossibly hard lift to switch from DocuSign.\n\nQuestions:\n\nDo you use Microsoft Purview to label and encrypt your data?\n\nIf so, have you hit this with signed or PDF/A files? How did you handle it: labeling before signing, a setting in your e-sign platform, a different protection method, or a documented exception?\n\nSide question: what PDF viewer/editor does your org standardize on?\n\nThis isn’t...",
    "sentiment": "neutral",
    "subreddit": "Office365",
    "event_date": "2026-10",
    "post_title": "Purview sensitivity labels with encryption won’t apply to signed PDF/A files from DocuSign. How are you handling this?",
    "prominence": "core",
    "source_url": "https://www.reddit.com/r/Office365/comments/1x1w02l/purview_sensitivity_labels_with_encryption_wont/",
    "entity_role": "vendor",
    "post_author": "In_Or_Out_Of_Scope",
    "upvote_ratio": 1,
    "mention_count": 2,
    "mention_surge": false,
    "subreddit_url": "https://www.reddit.com/r/Office365/",
    "total_upvotes": 1,
    "comments_total": 2,
    "total_comments": 2,
    "other_companies": [
      {
        "name": "Microsoft",
        "role": "partner",
        "domain": "microsoft.com"
      }
    ],
    "post_author_url": "https://www.reddit.com/user/In_Or_Out_Of_Scope/",
    "signal_category": "feedback",
    "comments_included": 2
  }
}

Long text fields are shortened on this page.

Looking up one signal by its id is free. Enrich costs 2 credits per signal returned; a call with no results is free.