{
  "schemaVersion": "1.2.0",
  "schema": "https://hivesilo.com/evidence/company-fact-sheet.schema.json",
  "slug": "microsoft-dynamics-365",
  "product": "Microsoft Dynamics 365",
  "url": "https://hivesilo.com/integrations/microsoft-dynamics-365",
  "title": "Microsoft Dynamics 365 Integration: Scores by Dataverse API | HiveSilo",
  "description": "Microsoft Dynamics 365 integration with HiveSilo: scored website buyers upserted to the Lead table through the Dataverse Web API, with access your administrator controls.",
  "reviewed": "2026-11-11",
  "connectionStatus": "available",
  "image": {
    "width": 1800,
    "height": 1195,
    "group": "crm",
    "alt": "Illustrative enterprise office at dusk for the Microsoft Dynamics 365 integration workflow",
    "heroVariants": [
      {
        "path": "/img/integrations/microsoft-dynamics-365-integration-crm-480.854e22807114.webp",
        "width": 480,
        "height": 319,
        "bytes": 21216
      },
      {
        "path": "/img/integrations/microsoft-dynamics-365-integration-crm-768.3a4946822424.webp",
        "width": 768,
        "height": 510,
        "bytes": 47770
      },
      {
        "path": "/img/integrations/microsoft-dynamics-365-integration-crm-1200.742eae743649.webp",
        "width": 1200,
        "height": 797,
        "bytes": 98032
      },
      {
        "path": "/img/integrations/microsoft-dynamics-365-integration-crm-1800.bc95e30e4f11.webp",
        "width": 1800,
        "height": 1195,
        "bytes": 169500
      }
    ],
    "socialImage": {
      "path": "/og/microsoft-dynamics-365-integration-intelligence.2be7baf1ef7c.png",
      "width": 1200,
      "height": 630,
      "bytes": 771733
    },
    "retiredSocialImages": [],
    "sourceSha256": "40f59dc928a0",
    "source": "AI-generated illustrative scene; not a vendor or customer facility",
    "illustrative": true
  },
  "content": {
    "inventoryId": "P703",
    "slug": "microsoft-dynamics-365",
    "product": "Microsoft Dynamics 365",
    "shortName": "Dynamics 365",
    "niche": "crm-platforms",
    "connectionStatus": "available",
    "reviewed": "2026-11-11",
    "contentVersion": "1.2.0",
    "title": "Microsoft Dynamics 365 Integration: Scores by Dataverse API | HiveSilo",
    "description": "Microsoft Dynamics 365 integration with HiveSilo: scored website buyers upserted to the Lead table through the Dataverse Web API, with access your administrator controls.",
    "primaryKeyword": "Microsoft Dynamics 365 integration",
    "secondaryKeywords": [
      "Dynamics 365 lead scoring integration",
      "Dataverse Web API lead upsert",
      "Dynamics 365 buyer intent data",
      "HiveSilo Dynamics 365"
    ],
    "sources": [
      {
        "id": "P703-D01",
        "title": "Microsoft Learn: Use the Microsoft Dataverse Web API",
        "url": "https://learn.microsoft.com/en-us/power-apps/developer/data-platform/webapi/overview",
        "supports": "The Dataverse Web API implements OData version 4.0 and can be called from any language that sends authenticated HTTP requests.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P703-D02",
        "title": "Microsoft Learn: Use OAuth authentication with Microsoft Dataverse",
        "url": "https://learn.microsoft.com/en-us/power-apps/developer/data-platform/authenticate-oauth",
        "supports": "Web API clients must use OAuth with Microsoft Entra ID as the identity provider; a server-to-server client connects as an application user bound to a registered app, using a client secret or certificate and the scope <environment-url>/.default, and that user does not consume a paid license.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P703-D03",
        "title": "Microsoft Learn: Manage application users in the Power Platform admin center",
        "url": "https://learn.microsoft.com/en-us/power-platform/admin/manage-application-users",
        "supports": "An administrator creates an unlicensed application user in an environment, assigns its business unit and security roles, and can edit those roles, deactivate the user or delete it once inactive; one application user per registered Microsoft Entra application per environment.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P703-D04",
        "title": "Microsoft Learn: Use Upsert to Create or Update a record",
        "url": "https://learn.microsoft.com/en-us/power-apps/developer/data-platform/use-upsert-insert-update-record",
        "supports": "A PATCH request to an entity set with key values in the URL is an upsert unless the If-Match: * header is sent; it creates the record when none matches and returns 204 No Content either way, or 201 and 200 with Prefer: return=representation; alternate keys are the expected way to identify records in data integration.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P703-D05",
        "title": "Microsoft Learn: Work with alternate keys",
        "url": "https://learn.microsoft.com/en-us/power-apps/developer/data-platform/define-alternate-keys-entity",
        "supports": "An alternate key lets a Dataverse column hold the unique identifier used by an external system; a table can have up to ten alternate key definitions, and key values containing certain characters such as / or + stop GET and PATCH by key from working.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P703-D06",
        "title": "Microsoft Learn: Lead table/entity reference (Microsoft Dynamics 365)",
        "url": "https://learn.microsoft.com/en-us/dynamics365/developer/reference/entities/lead",
        "supports": "The Lead table has EntitySetName leads and supports the Create, Update, Upsert and UpsertMultiple messages; columns include Subject, CompanyName, EMailAddress1, Description, LeadSourceCode and LeadQualityCode (display name Rating, choices Hot, Warm and Cold); the msdyn_LeadScore and msdyn_LeadGrade columns carry display names marked (Deprecated); the Lead_Annotation relationship links notes to a lead. The same page documents the Status column (Open, Qualified, Disqualified), the Qualifying Opportunity lookup, the Source Campaign lookup and the Web choice of Lead Source.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P703-D07",
        "title": "Microsoft Learn: annotation EntityType (Dataverse Web API reference)",
        "url": "https://learn.microsoft.com/en-us/power-apps/developer/data-platform/webapi/reference/annotation",
        "supports": "The annotation entity has display name Note, entity set path [organization URI]/api/data/v9.2/annotations, supports POST, GET, PATCH and DELETE, and carries the subject and notetext properties.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P703-D08",
        "title": "Microsoft Learn: Create and update column definitions using the Web API",
        "url": "https://learn.microsoft.com/en-us/power-apps/developer/data-platform/webapi/create-update-column-definitions-using-web-api",
        "supports": "Columns can be added to an existing table with a POST to EntityDefinitions(LogicalName='<table>')/Attributes; documented examples include string, integer, decimal, memo and choice columns.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P703-D09",
        "title": "Microsoft Learn: Use bulk operation messages",
        "url": "https://learn.microsoft.com/en-us/power-apps/developer/data-platform/bulk-operations",
        "supports": "The UpsertMultiple action performs upserts in bulk, identifying records by alternate key, and returns 204 No Content; Microsoft advises sending 100 to 1,000 records at a time; two records with the same key in one payload return an error.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P703-D10",
        "title": "Microsoft Learn: Service protection API limits",
        "url": "https://learn.microsoft.com/en-us/power-apps/developer/data-platform/api-limits",
        "supports": "Default limits per user and per web server: 6,000 requests within a five-minute sliding window, 20 minutes of combined execution time in that window, and 52 or more concurrent requests; the Web API returns 429 Too Many Requests with a Retry-After header; the values can change and vary by environment; entitlement limits are evaluated separately.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P703-D11",
        "title": "Microsoft Learn: Publish your app on Marketplace",
        "url": "https://learn.microsoft.com/en-us/power-platform/developer/marketplace/publish-app",
        "supports": "Listing an app on Microsoft Marketplace requires a Microsoft Partner Center account, a managed solution and a Marketplace package submitted through Partner Center. HiveSilo does not claim a marketplace listing.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P703-D12",
        "title": "Microsoft Learn: Contact table/entity reference (Microsoft Dataverse)",
        "url": "https://learn.microsoft.com/en-us/power-apps/developer/data-platform/reference/entities/contact",
        "supports": "The Contact table is described as a person with whom a business unit has a relationship, such as customer, supplier, and colleague; its EntitySetName is contacts; it supports the Create, Update, Upsert and UpsertMultiple messages; the Contact_Annotation relationship links notes to a contact.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P703-D13",
        "title": "Microsoft Learn: Account table/entity reference (Microsoft Dataverse)",
        "url": "https://learn.microsoft.com/en-us/power-apps/developer/data-platform/reference/entities/account",
        "supports": "The Account table is described as a business that represents a customer or potential customer; its EntitySetName is accounts; it supports the Create, Update, Upsert and UpsertMultiple messages and carries an Account Rating choice column.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P703-D14",
        "title": "Microsoft Learn: Opportunity table/entity reference (Microsoft Dynamics 365)",
        "url": "https://learn.microsoft.com/en-us/dynamics365/developer/reference/entities/opportunity",
        "supports": "The Opportunity table is described as a potential revenue-generating event, or sale to an account; its EntitySetName is opportunities; columns include Rating (Hot, Warm, Cold), Originating Lead, Status (Open, Won, Lost), Est. revenue, Actual Revenue and Actual Close Date.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P703-D15",
        "title": "Microsoft Learn: Security roles and privileges for Dataverse",
        "url": "https://learn.microsoft.com/en-us/power-platform/admin/security-roles-privileges",
        "supports": "Security roles define how users access records; table privileges include Read, Create, Delete, Write, Assign, Share, Append and Append To, each with an access level; privileges from several roles are cumulative; Append To on a record is what allows a note to be added to it.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P703-D16",
        "title": "Microsoft Learn: Manage Dataverse auditing",
        "url": "https://learn.microsoft.com/en-us/power-platform/admin/manage-dataverse-auditing",
        "supports": "Dataverse auditing logs changes to customer records, including create, update and delete operations, and helps answer who created or updated a record and when and which fields changed; it is configured at environment, table and column level, with a retention period the administrator selects.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P703-D17",
        "title": "Microsoft Learn: Sandbox environments",
        "url": "https://learn.microsoft.com/en-us/power-platform/admin/sandbox-environments",
        "supports": "A sandbox environment is any non-production environment of Microsoft Dataverse, isolated from production, described as the place to develop and test application changes with low risk; it is managed in the Power Platform admin center.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P703-D18",
        "title": "Microsoft Learn: Detect duplicate data using the Web API",
        "url": "https://learn.microsoft.com/en-us/power-apps/developer/data-platform/webapi/manage-duplicate-detection-create-update",
        "supports": "The MSCRM.SuppressDuplicateDetection request header, set to false, stops a Web API create or update when a duplicate is found; Dataverse includes default duplicate detection rules for accounts, contacts and leads; duplicate detection is suppressed by default when updating through the Web API.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P703-D19",
        "title": "Microsoft Learn: Column-level security",
        "url": "https://learn.microsoft.com/en-us/power-platform/admin/field-level-security",
        "supports": "Column-level security can prevent certain users from setting the value of a column or viewing its data; the configuration is organization-wide, applies to all data access requests and needs the system administrator role to set up.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P703-D20",
        "title": "Microsoft Learn: Power Platform environments overview",
        "url": "https://learn.microsoft.com/en-us/power-platform/admin/environments-overview",
        "supports": "Each environment is created under a Microsoft Entra tenant and is bound to a geographic location; the environment types include Production and Sandbox, and sandbox environments are used for development and testing, separate from production.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "HSF1",
        "title": "HiveSilo capability overview",
        "url": "https://hivesilo.com/evidence/features.md",
        "supports": "Published HiveSilo capabilities: buyer intelligence with Tier 1, Tier 2 and Tier 3 qualification, Revenue Seeker, AdBrain, offline conversion feedback and outcome measurement, AI Governance & Control, bot defense and client-controlled privacy; typical deployment of approximately 72 hours to set up and 7 days to live mapping and go-live, subject to fit, customer readiness and agreed scope.",
        "reviewed": "2026-11-11"
      }
    ],
    "hero": {
      "h1": "Dynamics 365. See which website leads are ready to buy.",
      "lede": "Dynamics 365 holds your leads and the work your sellers do on them. HiveSilo scores buyers on your own website and writes that evidence to the Lead row through the Dataverse Web API that Microsoft documents.",
      "imageLines": [
        "Your leads, in your environment.",
        "Website buying evidence beside them."
      ]
    },
    "problem": {
      "heading": "The lead is in the queue. How serious is it?",
      "summary": "Dynamics 365 records the enquiry. It did not watch the visits that came before it.",
      "question": "What should a seller know before opening a new lead?",
      "paragraphs": [
        "A web form creates a lead with a topic, a name and a company. The seller who picks it up sees the same few columns whether the person behind it shows strong buying intent or very little. Without more context, every new lead looks equally urgent.",
        "Dynamics 365 has its own rating, assignment and automation features, and those stay in charge of your process. HiveSilo contributes one thing they do not collect themselves: first-party behavior on your own website, scored for buying intent and screened for invalid traffic, then written to columns your administrator picks."
      ]
    },
    "value": {
      "heading": "Add website buying evidence to the lead row.",
      "summary": "HiveSilo does not change how your Dynamics 365 process runs. It writes a score, a tier and a short explanation to the lead, so your views, queues and reports can use them.",
      "decisions": [
        {
          "title": "Which lead to open first.",
          "body": "Sort new leads by observed buying intent, next to the rating your team already uses."
        },
        {
          "title": "How to open the conversation.",
          "body": "Read a short reason for the score in a note on the lead before you call."
        },
        {
          "title": "Which sources deserve budget.",
          "body": "Compare lead sources by buyer quality in your own Dynamics 365 views and charts."
        }
      ],
      "capabilities": [
        {
          "heading": "One lead per buyer, kept current.",
          "body": "HiveSilo sends a PATCH request addressed by an alternate key on the leads entity set. Microsoft documents that this request creates the row when no match exists and updates it when one does.",
          "output": "A single lead row per buyer, carrying the latest score and tier.",
          "sourceIds": [
            "P703-D04",
            "P703-D05",
            "P703-D06"
          ]
        },
        {
          "heading": "The explanation, as a note on the lead.",
          "body": "A short reason for the score and the suggested next step are posted as a Note, the annotation table in Dataverse, related to the lead through the documented Lead_Annotation relationship.",
          "output": "A note on the lead timeline that explains the score.",
          "sourceIds": [
            "P703-D06",
            "P703-D07"
          ]
        },
        {
          "heading": "Columns you own and can report on.",
          "body": "Score and tier land in columns your administrator selects or creates. The standard Rating column offers Hot, Warm and Cold, and custom columns can be added to the Lead table for numeric values.",
          "output": "Lead columns your own views, charts and flows can read.",
          "sourceIds": [
            "P703-D06",
            "P703-D08",
            "HS1"
          ]
        }
      ]
    },
    "integration": {
      "heading": "How HiveSilo connects to Dynamics 365",
      "statusNote": "The connection is activated for each client on request, inside that client's own Dynamics 365 environment, with the application user, security role and columns their administrator approves.",
      "intro": "Each row below names a route in Microsoft's public documentation for the Dataverse Web API, the API behind Dynamics 365 apps that use the Lead table. HiveSilo calls it outbound to write these rows. In this workflow it does not read lead status or opportunity outcomes back, and it does not ask Dynamics 365 to call into your systems.",
      "tableCaption": "What HiveSilo writes to Dynamics 365 and the documented route for each item",
      "flows": [
        {
          "sends": "A buyer who identifies themselves on your website",
          "lands": "A row in the Lead table, created or updated",
          "route": "PATCH to the leads entity set with alternate key values in the URL. Without an If-Match header, Dataverse treats the request as an upsert.",
          "sourceIds": [
            "P703-D04",
            "P703-D06"
          ]
        },
        {
          "sends": "A returning visitor who is already your customer",
          "lands": "The matching row in the Contact table, updated in place",
          "route": "The same PATCH upsert on the contacts entity set, addressed by an alternate key. The Contact reference lists Upsert among its messages. Which visitors go to Lead and which to Contact is part of the scope you agree.",
          "sourceIds": [
            "P703-D04",
            "P703-D12"
          ]
        },
        {
          "sends": "Buyer score and Tier 1, Tier 2 or Tier 3 qualification",
          "lands": "Lead columns your administrator selects",
          "route": "The body of the same upsert. The Lead reference documents Rating (Hot, Warm, Cold), Lead Source and Description; custom columns can be added through EntityDefinitions and its Attributes collection.",
          "sourceIds": [
            "P703-D06",
            "P703-D08"
          ]
        },
        {
          "sends": "A short reason for the score and a suggested next step",
          "lands": "A Note related to the lead",
          "route": "POST to the annotations entity set, using the subject and notetext properties. The Lead reference documents the Lead_Annotation relationship.",
          "sourceIds": [
            "P703-D06",
            "P703-D07"
          ]
        },
        {
          "sends": "Campaign and source context",
          "lands": "Lead Source or columns your administrator selects",
          "route": "The body of the same upsert, written to the Lead Source choice column or to custom columns on the Lead table.",
          "sourceIds": [
            "P703-D06",
            "P703-D08"
          ]
        },
        {
          "sends": "Many scored buyers at once",
          "lands": "Lead rows, in batches",
          "route": "The UpsertMultiple action, which the Lead table lists among its messages. Microsoft advises 100 to 1,000 records per request.",
          "sourceIds": [
            "P703-D06",
            "P703-D09"
          ]
        }
      ],
      "facts": [
        {
          "label": "Access you grant",
          "body": "OAuth through Microsoft Entra ID. Your administrator creates an application user in the environment, bound to a registered app, and assigns it a custom security role. Microsoft states that an application user does not consume a paid license.",
          "sourceIds": [
            "P703-D02",
            "P703-D03"
          ]
        },
        {
          "label": "Matching key",
          "body": "An alternate key on the Lead table holds the identifier HiveSilo uses for matching. A table can have up to ten alternate keys, and Microsoft advises against key values that contain characters such as / or +.",
          "sourceIds": [
            "P703-D05"
          ]
        },
        {
          "label": "Duplicate detection",
          "body": "Dataverse includes default duplicate detection rules for accounts, contacts and leads. Microsoft documents the MSCRM.SuppressDuplicateDetection request header: set to false, a create or update is not completed when a duplicate is found. Your administrator decides whether that header is used.",
          "sourceIds": [
            "P703-D18"
          ]
        },
        {
          "label": "Limits to plan for",
          "body": "Default service protection limits apply per user and per web server: 6,000 requests in a five-minute sliding window, 20 minutes of combined execution time and 52 or more concurrent requests. Dataverse answers 429 with a Retry-After header. Microsoft says these values can change, and entitlement limits are counted separately.",
          "sourceIds": [
            "P703-D10"
          ]
        },
        {
          "label": "Columns marked deprecated",
          "body": "The Lead reference labels msdyn_LeadScore and msdyn_LeadGrade as (Deprecated). Scores are mapped to the standard Rating column or to custom columns your administrator creates, not to those columns.",
          "sourceIds": [
            "P703-D06",
            "P703-D08"
          ]
        },
        {
          "label": "How to revoke",
          "body": "Your administrator can change the application user's security roles, deactivate it, or delete it once inactive, in the Power Platform admin center.",
          "sourceIds": [
            "P703-D03"
          ]
        }
      ],
      "questionsHeading": "Who, what, when, where, how and why",
      "questions": [
        {
          "label": "Who",
          "body": "Organizations that work leads in Dynamics 365 and want sellers to see buying intent from the company website. A Power Platform administrator creates the application user and its security role.",
          "sourceIds": [
            "P703-D03"
          ]
        },
        {
          "label": "What",
          "body": "A buyer score, a Tier 1, Tier 2 or Tier 3 qualification, a short reason for them, a suggested next step and campaign context, written to the Lead or Contact row and to a related Note.",
          "sourceIds": [
            "P703-D06",
            "P703-D07",
            "P703-D12"
          ]
        },
        {
          "label": "When",
          "body": "When a visitor identifies themselves on your website, for example through an enquiry form, and again when a returning buyer's score changes.",
          "sourceIds": [
            "HS1"
          ]
        },
        {
          "label": "Where",
          "body": "In your own Dynamics 365 environment, on the lead your sellers already open. Your team does not have to check a second customer database.",
          "sourceIds": [
            "P703-D04",
            "HS4"
          ]
        },
        {
          "label": "How",
          "body": "Outbound HTTPS calls to the Dataverse Web API, an OData version 4.0 service, authorized by Microsoft Entra ID and matched on an alternate key.",
          "sourceIds": [
            "P703-D01",
            "P703-D02",
            "P703-D04"
          ]
        },
        {
          "label": "Why",
          "body": "Dynamics 365 holds the relationship and the sales process. HiveSilo observes how the buyer behaved on your website before the enquiry. The seller reads both on one row.",
          "sourceIds": [
            "HS1",
            "HS2"
          ]
        }
      ],
      "summary": "Dynamics 365 is the system of record for leads, contacts, accounts and opportunities. HiveSilo scores buying intent on your own website, screens invalid traffic and writes a Tier 1, Tier 2 or Tier 3 qualification to the Lead or Contact row through the Dataverse Web API, as an application user your administrator controls. Customer identities stay in your environment and your own confidential environment.",
      "summarySourceIds": [
        "P703-D03",
        "P703-D04",
        "HSF1",
        "HS4"
      ],
      "features": {
        "heading": "Where each HiveSilo capability meets Dynamics 365",
        "intro": "Each row pairs a published HiveSilo capability with the Dynamics 365 or Dataverse feature it works with. Scope is agreed for each client. The connection writes; any row that needs HiveSilo to read from Dynamics 365 says so and needs a separate privilege from your administrator.",
        "rows": [
          {
            "capability": "Buyer intelligence and three-tier qualification",
            "feature": "The Lead and Contact tables: the Rating column on Lead (Hot, Warm, Cold), custom columns, and an alternate key for upsert",
            "gain": "Sellers see a buyer score and a Tier 1, Tier 2 or Tier 3 qualification on the row they already open, and a returning buyer updates that row instead of adding another.",
            "sourceIds": [
              "P703-D05",
              "P703-D06",
              "P703-D12",
              "HSF1"
            ]
          },
          {
            "capability": "AI firewall, bot defense and site protection",
            "feature": "Duplicate detection rules for leads, contacts and accounts, applied to Web API writes through the MSCRM.SuppressDuplicateDetection header",
            "gain": "Invalid traffic is screened before it becomes a lead, and the rows that are written can be held to the duplicate rules you already run.",
            "sourceIds": [
              "P703-D18",
              "HSF1"
            ]
          },
          {
            "capability": "AdBrain",
            "feature": "The Lead Source choice column and the Source Campaign lookup on the Lead table",
            "gain": "Your own Dynamics 365 views and charts can compare sources and campaigns by qualified demand as well as by volume.",
            "sourceIds": [
              "P703-D06",
              "HSF1"
            ]
          },
          {
            "capability": "Offline conversions, qualified-demand scaling and outcome measurement",
            "feature": "Lead Status (Open, Qualified, Disqualified), the Qualifying Opportunity lookup, and Opportunity Status (Open, Won, Lost) with Actual Revenue",
            "gain": "With a read privilege you grant, qualified leads and won opportunities can inform the qualified-buyer feedback sent to supported advertising platforms.",
            "sourceIds": [
              "P703-D06",
              "P703-D14",
              "HSF1"
            ]
          },
          {
            "capability": "Revenue Seeker",
            "feature": "Contact, Account and Opportunity rows already in your environment",
            "gain": "With a read privilege you grant, Dynamics 365 can be one of the authorized sources searched for revenue opportunities, which go to your own salespeople. HiveSilo cannot see those records.",
            "sourceIds": [
              "P703-D12",
              "P703-D13",
              "P703-D14",
              "HSF1"
            ]
          },
          {
            "capability": "AI Governance & Control",
            "feature": "The application user, a custom security role with table privileges such as Create, Write, Append and Append To, and Dataverse auditing",
            "gain": "Every write runs through a user whose privileges your administrator sets and can remove, auditing you turn on can record who created or updated a row and when, and a person decides the outreach.",
            "sourceIds": [
              "P703-D03",
              "P703-D15",
              "P703-D16",
              "HS6"
            ]
          },
          {
            "capability": "Client-controlled privacy and verification",
            "feature": "Microsoft Entra ID authorization, column-level security, and an environment bound to the geographic location you chose",
            "gain": "Customer identities stay in your environment, in its geography, and in your confidential environment, outside HiveSilo's visibility. Column-level security can limit who views the score columns.",
            "sourceIds": [
              "P703-D02",
              "P703-D19",
              "P703-D20",
              "HS4",
              "HSF1"
            ]
          }
        ]
      },
      "capture": {
        "heading": "How the buying signals are captured and linked",
        "paragraphs": [
          "Lightweight first-party instrumentation on your own website reads pseudonymous behavior from your visitors, and HiveSilo scores those non-PII signals. Anything that could identify a person goes from your website into your own per-tenant confidential enclave, not into HiveSilo's shared platform.",
          "An anonymous session has a score but no row in Dynamics 365. The link is made when the visitor identifies themselves on your website, for example through an enquiry form. That match happens inside your enclave, and the scored Lead or Contact row is written to your environment from there."
        ],
        "sourceIds": [
          "HS3",
          "HS4"
        ]
      },
      "setup": {
        "heading": "What your Dynamics 365 team does",
        "intro": "The connection is configuration in your environment plus activation on the HiveSilo side. These are the steps on your side, as Microsoft documents them.",
        "steps": [
          {
            "title": "Register the app.",
            "body": "Register an application in Microsoft Entra ID and give it a client secret or a certificate. Microsoft documents this as the way to connect as an app.",
            "sourceIds": [
              "P703-D02"
            ]
          },
          {
            "title": "Create the application user.",
            "body": "In the Power Platform admin center, create an application user for that app in the environment and choose its business unit. One application user is allowed per registered app in an environment.",
            "sourceIds": [
              "P703-D03"
            ]
          },
          {
            "title": "Assign a narrow security role.",
            "body": "Give the application user a custom security role with only the table privileges the agreed writes need: Create and Write on the tables in scope, and Append and Append To so a Note can be attached.",
            "sourceIds": [
              "P703-D03",
              "P703-D15"
            ]
          },
          {
            "title": "Add the key and the score columns.",
            "body": "Define an alternate key on the Lead table, and on Contact if it is in scope, and choose or create the columns that hold the score, tier and source context.",
            "sourceIds": [
              "P703-D05",
              "P703-D08"
            ]
          },
          {
            "title": "Test in a sandbox environment first.",
            "body": "Microsoft describes a sandbox environment as non-production, isolated from production, and the place to test changes with low risk. Check column mapping, the alternate key and your duplicate rules there.",
            "sourceIds": [
              "P703-D17",
              "P703-D18"
            ]
          },
          {
            "title": "Decide on auditing.",
            "body": "If you want a record of each write, turn on Dataverse auditing for the environment, the table and the columns in scope, and select a retention period.",
            "sourceIds": [
              "P703-D16"
            ]
          },
          {
            "title": "Switch on production.",
            "body": "Create the application user and assign the same role in your production environment once the sandbox result is accepted.",
            "sourceIds": [
              "P703-D03"
            ]
          }
        ],
        "timeline": "HiveSilo's published typical deployment is approximately 72 hours to set up and 7 days to live mapping and go-live, subject to fit, customer readiness and agreed scope. The Dynamics 365 steps above run on your own change process.",
        "timelineSourceIds": [
          "HSF1"
        ]
      },
      "preview": {
        "heading": "What the lead owner sees",
        "note": "Illustrative example, not a Dynamics 365 screen. Column names are chosen by your administrator. The score shown is HiveSilo's published specimen.",
        "sourceIds": [
          "HS8"
        ],
        "fields": [
          {
            "label": "Lead Source",
            "value": "Web"
          },
          {
            "label": "Rating",
            "value": "Hot"
          },
          {
            "label": "HiveSilo buyer score (custom column)",
            "value": "3,790 of 5,000"
          },
          {
            "label": "HiveSilo qualification (custom column)",
            "value": "Tier 1"
          }
        ],
        "task": {
          "label": "Note on the lead",
          "subject": "Open first: strong buying intent on the website",
          "body": "Strong buying intent on your website this week. Traffic screened as genuine. Suggested next step: call today."
        }
      }
    },
    "example": {
      "heading": "Two new leads before the morning stand-up.",
      "setup": "Illustrative workflow: two leads reach Dynamics 365 overnight. Both carry a topic and a company name. One shows strong buying intent and is qualified Tier 1; the other shows little and is Tier 3.",
      "nativeBaseline": "Dynamics 365 creates both leads and applies the assignment and rating rules you have configured. That process is unchanged.",
      "inputs": [
        "Each lead as Dynamics 365 created it, with its owner and lead source.",
        "HiveSilo's score and tier for the website sessions behind each enquiry.",
        "A short reason for each score, including any invalid-traffic concern."
      ],
      "decision": "The seller opens the Tier 1 buyer first and handles the second lead according to its lower score.",
      "output": "A lead row whose columns show the score and tier, with a Note that explains them.",
      "owner": "The lead owner in Dynamics 365 decides the outreach. HiveSilo supplies evidence; it does not contact the buyer in this workflow.",
      "hold": "Hold automated outreach when the score is low, the traffic-quality concern is unresolved or contact permission is unclear.",
      "record": "Qualify or disqualify the lead in Dynamics 365 as usual. Your own views and reports can then compare the score column with the outcome. HiveSilo does not read that outcome back in this workflow.",
      "sourceIds": [
        "P703-D06",
        "P703-D07"
      ]
    },
    "governance": {
      "intro": "A score is advice to the seller. The seller and your rules still decide.",
      "example": "Agree which Dynamics 365 actions a score may drive and which need a person. Writing a column is different from reassigning a lead or starting a sequence. Give the application user a security role that covers only the tables and columns in scope, and keep any automation that reads the score under your own administrator's control."
    },
    "privacy": {
      "intro": "Your leads stay in your Dynamics 365 environment.",
      "detail": "The lead's identity is written to your own Dynamics 365 environment from the environment you control. HiveSilo's shared platform works with permitted non-PII signals and scores. The security role your administrator assigns limits what the application user can write, and Dynamics 365 security continues to govern who can read it."
    },
    "outcomes": {
      "intro": "Bring website buying evidence to the Dynamics 365 lead, so prioritization, the first call and the source review all draw on the same facts.",
      "panels": [
        "Sort new Dynamics 365 leads by observed buying intent before a seller opens them.",
        "See which sources and pages your best-scoring Dynamics 365 leads share, then invest more there.",
        "Question spend on sources whose leads score low and seldom qualify.",
        "Screen invalid traffic before it becomes a lead in a seller's queue.",
        "Find open Dynamics 365 leads whose owners have gone quiet while the buyer shows renewed buying intent on your website."
      ]
    },
    "fit": {
      "intro": "Most useful where Dynamics 365 is the system of record for leads and the website is a material source of them.",
      "good": [
        "Sales teams that work the Lead table in Dynamics 365 every day.",
        "Businesses with considered, high-value purchases where the order of follow-up matters.",
        "Organizations with a Power Platform administrator who can create an application user, a security role and an alternate key."
      ],
      "consider": [
        "The rating, assignment and automation features already in Dynamics 365 may answer the question for some teams.",
        "An alternate key on the Lead table has to exist before upserts can match on it.",
        "Service protection limits apply per user, so plan volume with your administrator."
      ]
    },
    "connection": {
      "heading": "Agree the environment, the key and the security role.",
      "paragraphs": [
        "Confirm the Dynamics 365 environment URL, the alternate key used for matching, and the Lead columns that will hold the score, tier and source context. Your administrator registers the app in Microsoft Entra ID, creates the application user and assigns a security role limited to those writes.",
        "The connection is available and is activated for each client on request. Microsoft's documentation establishes what the Dataverse Web API supports; your environment's configuration, your agreements with Microsoft and your agreement with HiveSilo determine the scope that is switched on."
      ],
      "sourceIds": [
        "P703-D02",
        "P703-D03",
        "P703-D05",
        "HS10"
      ]
    },
    "faqs": [
      {
        "question": "Does HiveSilo connect to Microsoft Dynamics 365?",
        "answer": "Yes. The Dynamics 365 connection is available and is activated for each client on request. It uses the Dataverse Web API that Microsoft documents, with access your administrator grants.",
        "sourceIds": [
          "P703-D01",
          "HS2"
        ]
      },
      {
        "question": "Which Dynamics 365 tables does HiveSilo write to?",
        "answer": "The Lead table for new buyers and the Contact table for visitors who are already your customers, both by upsert on an alternate key, plus a Note (annotation) for the explanation and next step. Other tables, including Account, Opportunity and custom tables, are scoped for each client through the same Web API. Your administrator selects the columns.",
        "sourceIds": [
          "P703-D04",
          "P703-D06",
          "P703-D07",
          "P703-D12",
          "P703-D13"
        ]
      },
      {
        "question": "Will it create duplicate leads?",
        "answer": "The write is an upsert addressed by an alternate key. Microsoft documents that the request updates the matching row and creates one only when no row matches. Matching depends on the alternate key your administrator defines.",
        "sourceIds": [
          "P703-D04",
          "P703-D05"
        ]
      },
      {
        "question": "Does the integration need a paid user license?",
        "answer": "Microsoft's documentation says a server-to-server integration connects as an application user bound to a registered app, and that this approach does not consume a paid license. Your own licensing terms with Microsoft still apply.",
        "sourceIds": [
          "P703-D02",
          "P703-D03"
        ]
      },
      {
        "question": "How is access granted and removed, and can we test first?",
        "answer": "Your administrator registers an app in Microsoft Entra ID, creates an application user for it in the environment and assigns a security role. They can change the roles, deactivate the user or delete it once inactive. Microsoft documents sandbox environments, isolated from production, for testing, and the connection can be pointed at a sandbox first.",
        "sourceIds": [
          "P703-D02",
          "P703-D03",
          "P703-D17"
        ]
      },
      {
        "question": "Does HiveSilo read data back from Dynamics 365?",
        "answer": "Not in this workflow. HiveSilo writes the score, tier and explanation; comparing score with outcome happens in your own views and reports. Reading outcomes back would need a separate Read privilege on the security role, which you would have to grant. Each write counts toward the service protection limits, 6,000 requests per user in a five-minute sliding window by default, and Dataverse answers 429 with a Retry-After header when a limit is reached.",
        "sourceIds": [
          "P703-D10",
          "P703-D15"
        ]
      },
      {
        "question": "Does Dynamics 365 already rate leads?",
        "answer": "Yes. The Lead table has a standard Rating column with Hot, Warm and Cold, and Dynamics 365 offers its own assignment and automation. HiveSilo adds first-party evidence from your own website, including traffic-quality screening, to the same lead.",
        "sourceIds": [
          "P703-D06",
          "HS1"
        ]
      },
      {
        "question": "Is HiveSilo listed on Microsoft Marketplace?",
        "answer": "No listing is claimed. Microsoft documents a Partner Center submission process for apps listed on its Marketplace. This connection is set up directly in your environment with an application user your administrator creates.",
        "sourceIds": [
          "P703-D11"
        ]
      }
    ],
    "relationshipContext": {
      "privacyContext": "The lead's identity is written to your own Dynamics 365 environment from the environment you control. HiveSilo's shared platform receives permitted non-PII signals and scores. The application user's security role and Dynamics 365 security continue to govern what is written and who can read it.",
      "diagramLabels": [
        "Customer identities stay in your Dynamics 365 environment",
        "Permitted non-PII website signals and buyer scores",
        "HiveSilo: buyer score, tier and reasons"
      ],
      "reviewIntentSentences": [
        "A Microsoft Dynamics 365 review should start with the rating, assignment and automation already configured in your environment.",
        "A Microsoft Dynamics 365 review of the connection should confirm the application user's security role and the columns it may write.",
        "When you review Microsoft Dynamics 365 with HiveSilo, ask which seller decision a website buyer score would change."
      ],
      "sourceIds": [
        "P703-D02",
        "P703-D03",
        "HS3",
        "HS4"
      ]
    }
  },
  "shared": {
    "privacyModel": "Customer identities and re-identifiable data stay in the customer-controlled environment; only permitted non-PII signals and scores cross the configured boundary. Account, billing and support records are separate.",
    "governanceSteps": [
      {
        "title": "Request",
        "detail": "An AI proposes an action"
      },
      {
        "title": "Check",
        "detail": "Policy and authority"
      },
      {
        "title": "Approve",
        "detail": "Named owner, when required"
      },
      {
        "title": "Act",
        "detail": "Within permitted scope"
      },
      {
        "title": "Record",
        "detail": "Keep the action, outcome and accountable owner traceable."
      }
    ],
    "outcomes": [
      {
        "value": "3,790",
        "prefix": "",
        "suffix": "of 5,000",
        "label": "UHNW buyer score",
        "note": "Illustrative score"
      },
      {
        "value": "4–6×",
        "prefix": "",
        "suffix": "",
        "label": "Reported conversion lift",
        "note": "Closed-revenue outcomes"
      },
      {
        "value": "31%",
        "prefix": "Up to",
        "suffix": "",
        "label": "Reported ad-spend savings",
        "note": "Bot and invalid-traffic filtering"
      },
      {
        "value": "99.9999%",
        "prefix": "",
        "suffix": "",
        "label": "Bot detection",
        "note": "Observed client results"
      },
      {
        "value": "5–21%",
        "prefix": "",
        "suffix": "",
        "label": "Revenue lift from existing data",
        "note": "HiveSilo-reported client results"
      }
    ],
    "outcomeContext": "Published outcomes include client-reported results and illustrative, unaudited ranges. The owned-data revenue range was supplied by HiveSilo; request the measurement context in your briefing. Results vary.",
    "botDetectionGoal": "99.9999999% is a goal, not an achieved result."
  },
  "sources": [
    {
      "id": "P703-D01",
      "title": "Microsoft Learn: Use the Microsoft Dataverse Web API",
      "url": "https://learn.microsoft.com/en-us/power-apps/developer/data-platform/webapi/overview",
      "supports": "The Dataverse Web API implements OData version 4.0 and can be called from any language that sends authenticated HTTP requests.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P703-D02",
      "title": "Microsoft Learn: Use OAuth authentication with Microsoft Dataverse",
      "url": "https://learn.microsoft.com/en-us/power-apps/developer/data-platform/authenticate-oauth",
      "supports": "Web API clients must use OAuth with Microsoft Entra ID as the identity provider; a server-to-server client connects as an application user bound to a registered app, using a client secret or certificate and the scope <environment-url>/.default, and that user does not consume a paid license.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P703-D03",
      "title": "Microsoft Learn: Manage application users in the Power Platform admin center",
      "url": "https://learn.microsoft.com/en-us/power-platform/admin/manage-application-users",
      "supports": "An administrator creates an unlicensed application user in an environment, assigns its business unit and security roles, and can edit those roles, deactivate the user or delete it once inactive; one application user per registered Microsoft Entra application per environment.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P703-D04",
      "title": "Microsoft Learn: Use Upsert to Create or Update a record",
      "url": "https://learn.microsoft.com/en-us/power-apps/developer/data-platform/use-upsert-insert-update-record",
      "supports": "A PATCH request to an entity set with key values in the URL is an upsert unless the If-Match: * header is sent; it creates the record when none matches and returns 204 No Content either way, or 201 and 200 with Prefer: return=representation; alternate keys are the expected way to identify records in data integration.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P703-D05",
      "title": "Microsoft Learn: Work with alternate keys",
      "url": "https://learn.microsoft.com/en-us/power-apps/developer/data-platform/define-alternate-keys-entity",
      "supports": "An alternate key lets a Dataverse column hold the unique identifier used by an external system; a table can have up to ten alternate key definitions, and key values containing certain characters such as / or + stop GET and PATCH by key from working.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P703-D06",
      "title": "Microsoft Learn: Lead table/entity reference (Microsoft Dynamics 365)",
      "url": "https://learn.microsoft.com/en-us/dynamics365/developer/reference/entities/lead",
      "supports": "The Lead table has EntitySetName leads and supports the Create, Update, Upsert and UpsertMultiple messages; columns include Subject, CompanyName, EMailAddress1, Description, LeadSourceCode and LeadQualityCode (display name Rating, choices Hot, Warm and Cold); the msdyn_LeadScore and msdyn_LeadGrade columns carry display names marked (Deprecated); the Lead_Annotation relationship links notes to a lead. The same page documents the Status column (Open, Qualified, Disqualified), the Qualifying Opportunity lookup, the Source Campaign lookup and the Web choice of Lead Source.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P703-D07",
      "title": "Microsoft Learn: annotation EntityType (Dataverse Web API reference)",
      "url": "https://learn.microsoft.com/en-us/power-apps/developer/data-platform/webapi/reference/annotation",
      "supports": "The annotation entity has display name Note, entity set path [organization URI]/api/data/v9.2/annotations, supports POST, GET, PATCH and DELETE, and carries the subject and notetext properties.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P703-D08",
      "title": "Microsoft Learn: Create and update column definitions using the Web API",
      "url": "https://learn.microsoft.com/en-us/power-apps/developer/data-platform/webapi/create-update-column-definitions-using-web-api",
      "supports": "Columns can be added to an existing table with a POST to EntityDefinitions(LogicalName='<table>')/Attributes; documented examples include string, integer, decimal, memo and choice columns.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P703-D09",
      "title": "Microsoft Learn: Use bulk operation messages",
      "url": "https://learn.microsoft.com/en-us/power-apps/developer/data-platform/bulk-operations",
      "supports": "The UpsertMultiple action performs upserts in bulk, identifying records by alternate key, and returns 204 No Content; Microsoft advises sending 100 to 1,000 records at a time; two records with the same key in one payload return an error.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P703-D10",
      "title": "Microsoft Learn: Service protection API limits",
      "url": "https://learn.microsoft.com/en-us/power-apps/developer/data-platform/api-limits",
      "supports": "Default limits per user and per web server: 6,000 requests within a five-minute sliding window, 20 minutes of combined execution time in that window, and 52 or more concurrent requests; the Web API returns 429 Too Many Requests with a Retry-After header; the values can change and vary by environment; entitlement limits are evaluated separately.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P703-D11",
      "title": "Microsoft Learn: Publish your app on Marketplace",
      "url": "https://learn.microsoft.com/en-us/power-platform/developer/marketplace/publish-app",
      "supports": "Listing an app on Microsoft Marketplace requires a Microsoft Partner Center account, a managed solution and a Marketplace package submitted through Partner Center. HiveSilo does not claim a marketplace listing.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P703-D12",
      "title": "Microsoft Learn: Contact table/entity reference (Microsoft Dataverse)",
      "url": "https://learn.microsoft.com/en-us/power-apps/developer/data-platform/reference/entities/contact",
      "supports": "The Contact table is described as a person with whom a business unit has a relationship, such as customer, supplier, and colleague; its EntitySetName is contacts; it supports the Create, Update, Upsert and UpsertMultiple messages; the Contact_Annotation relationship links notes to a contact.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P703-D13",
      "title": "Microsoft Learn: Account table/entity reference (Microsoft Dataverse)",
      "url": "https://learn.microsoft.com/en-us/power-apps/developer/data-platform/reference/entities/account",
      "supports": "The Account table is described as a business that represents a customer or potential customer; its EntitySetName is accounts; it supports the Create, Update, Upsert and UpsertMultiple messages and carries an Account Rating choice column.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P703-D14",
      "title": "Microsoft Learn: Opportunity table/entity reference (Microsoft Dynamics 365)",
      "url": "https://learn.microsoft.com/en-us/dynamics365/developer/reference/entities/opportunity",
      "supports": "The Opportunity table is described as a potential revenue-generating event, or sale to an account; its EntitySetName is opportunities; columns include Rating (Hot, Warm, Cold), Originating Lead, Status (Open, Won, Lost), Est. revenue, Actual Revenue and Actual Close Date.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P703-D15",
      "title": "Microsoft Learn: Security roles and privileges for Dataverse",
      "url": "https://learn.microsoft.com/en-us/power-platform/admin/security-roles-privileges",
      "supports": "Security roles define how users access records; table privileges include Read, Create, Delete, Write, Assign, Share, Append and Append To, each with an access level; privileges from several roles are cumulative; Append To on a record is what allows a note to be added to it.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P703-D16",
      "title": "Microsoft Learn: Manage Dataverse auditing",
      "url": "https://learn.microsoft.com/en-us/power-platform/admin/manage-dataverse-auditing",
      "supports": "Dataverse auditing logs changes to customer records, including create, update and delete operations, and helps answer who created or updated a record and when and which fields changed; it is configured at environment, table and column level, with a retention period the administrator selects.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P703-D17",
      "title": "Microsoft Learn: Sandbox environments",
      "url": "https://learn.microsoft.com/en-us/power-platform/admin/sandbox-environments",
      "supports": "A sandbox environment is any non-production environment of Microsoft Dataverse, isolated from production, described as the place to develop and test application changes with low risk; it is managed in the Power Platform admin center.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P703-D18",
      "title": "Microsoft Learn: Detect duplicate data using the Web API",
      "url": "https://learn.microsoft.com/en-us/power-apps/developer/data-platform/webapi/manage-duplicate-detection-create-update",
      "supports": "The MSCRM.SuppressDuplicateDetection request header, set to false, stops a Web API create or update when a duplicate is found; Dataverse includes default duplicate detection rules for accounts, contacts and leads; duplicate detection is suppressed by default when updating through the Web API.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P703-D19",
      "title": "Microsoft Learn: Column-level security",
      "url": "https://learn.microsoft.com/en-us/power-platform/admin/field-level-security",
      "supports": "Column-level security can prevent certain users from setting the value of a column or viewing its data; the configuration is organization-wide, applies to all data access requests and needs the system administrator role to set up.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P703-D20",
      "title": "Microsoft Learn: Power Platform environments overview",
      "url": "https://learn.microsoft.com/en-us/power-platform/admin/environments-overview",
      "supports": "Each environment is created under a Microsoft Entra tenant and is bound to a geographic location; the environment types include Production and Sandbox, and sandbox environments are used for development and testing, separate from production.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "HSF1",
      "title": "HiveSilo capability overview",
      "url": "https://hivesilo.com/evidence/features.md",
      "supports": "Published HiveSilo capabilities: buyer intelligence with Tier 1, Tier 2 and Tier 3 qualification, Revenue Seeker, AdBrain, offline conversion feedback and outcome measurement, AI Governance & Control, bot defense and client-controlled privacy; typical deployment of approximately 72 hours to set up and 7 days to live mapping and go-live, subject to fit, customer readiness and agreed scope.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "HS0",
      "title": "HiveSilo: industry coverage",
      "url": "https://hivesilo.com",
      "supports": "First-party description of buyer intelligence across 12 luxury niches.",
      "reviewed": "2026-10-25"
    },
    {
      "id": "HS1",
      "title": "HiveSilo: platform",
      "url": "https://hivesilo.com/platform",
      "supports": "Published intent, sales-prioritization and traffic-quality capabilities.",
      "reviewed": "2026-10-25"
    },
    {
      "id": "HS2",
      "title": "HiveSilo: integration scope",
      "url": "https://hivesilo.com/integrations",
      "supports": "Named destinations, scoped activation and customer-controlled dispatch.",
      "reviewed": "2026-10-25"
    },
    {
      "id": "HS3",
      "title": "HiveSilo: security architecture",
      "url": "https://hivesilo.com/security-architecture",
      "supports": "Documented confidential processing, BYOK and customer control.",
      "reviewed": "2026-10-25"
    },
    {
      "id": "HS4",
      "title": "HiveSilo: data handling",
      "url": "https://hivesilo.com/data-handling",
      "supports": "Customer identity custody, pseudonymous-data boundaries and separate account records.",
      "reviewed": "2026-10-25"
    },
    {
      "id": "HS5",
      "title": "HiveSilo: published outcomes",
      "url": "https://hivesilo.com/case-studies",
      "supports": "Existing first-party outcomes material, with client-reported and illustrative descriptions.",
      "reviewed": "2026-10-25"
    },
    {
      "id": "HS6",
      "title": "HiveSilo: AI agentic governance",
      "url": "https://hivesilo.com/ai-agentic-governance",
      "supports": "Published pre-action policy checks, default denial, human checkpoints, scoped stop controls and governance receipts.",
      "reviewed": "2026-10-25"
    },
    {
      "id": "HS7",
      "title": "HiveSilo: AI implementation layer",
      "url": "https://hivesilo.com/ai-implementation-layer",
      "supports": "Published combined implementation model for intelligence, confidential processing and AI governance.",
      "reviewed": "2026-10-25"
    },
    {
      "id": "HS8",
      "title": "HiveSilo: bot-detection results and buyer-score specimen",
      "url": "https://hivesilo.com/",
      "supports": "The homepage presents 99.9999% bot detection as observed client results, 99.9999999% as a goal, and a 3,790-of-5,000 UHNW buyer-score specimen.",
      "reviewed": "2026-10-25"
    },
    {
      "id": "HS9",
      "title": "HiveSilo: owned-data revenue result briefing",
      "url": "https://hivesilo.com/contact",
      "supports": "HiveSilo supplied a 5–21% client revenue increase range for existing-data workflows on 25 October 2026.",
      "reviewed": "2026-10-25"
    },
    {
      "id": "HS10",
      "title": "HiveSilo: enterprise agreements and responsibility",
      "url": "https://hivesilo.com/terms",
      "supports": "Signed enterprise agreements govern the engagement and take precedence over website summaries.",
      "reviewed": "2026-10-26"
    }
  ],
  "articleText": "Enterprise CRM & customer data Microsoft Dynamics 365 + HiveSilo Available View scope HiveSilo / Integrations / Microsoft Dynamics 365 Dynamics 365. See which website leads are ready to buy. Dynamics 365 holds your leads and the work your sellers do on them. HiveSilo scores buyers on your own website and writes that evidence to the Lead row through the Dataverse Web API that Microsoft documents. Contact HiveSilo Explore the fit Start with a conversation. No client records needed. Your leads, in your environment. Website buying evidence beside them. Your client list stays yours. The value AI control Your data What you could gain Let’s talk FAQs & evidence The lead is in the queue. How serious is it? Dynamics 365 records the enquiry. It did not watch the visits that came before it. What should a seller know before opening a new lead? A web form creates a lead with a topic, a name and a company. The seller who picks it up sees the same few columns whether the person behind it shows strong buying intent or very little. Without more context, every new lead looks equally urgent. Dynamics 365 has its own rating, assignment and automation features, and those stay in charge of your process. HiveSilo contributes one thing they do not collect themselves: first-party behavior on your own website, scored for buying intent and screened for invalid traffic, then written to columns your administrator picks. A Microsoft Dynamics 365 review should start with the rating, assignment and automation already configured in your environment. [P703-D02] [P703-D03] [HS3] [HS4] Add website buying evidence to the lead row. HiveSilo does not change how your Dynamics 365 process runs. It writes a score, a tier and a short explanation to the lead, so your views, queues and reports can use them. Talk through your use case Which lead to open first. Sort new leads by observed buying intent, next to the rating your team already uses. How to open the conversation. Read a short reason for the score in a note on the lead before you call. Which sources deserve budget. Compare lead sources by buyer quality in your own Dynamics 365 views and charts. Available The connection is activated for each client on request, inside that client's own Dynamics 365 environment, with the application user, security role and columns their administrator approves. How HiveSilo connects to Dynamics 365 Dynamics 365 is the system of record for leads, contacts, accounts and opportunities. HiveSilo scores buying intent on your own website, screens invalid traffic and writes a Tier 1, Tier 2 or Tier 3 qualification to the Lead or Contact row through the Dataverse Web API, as an application user your administrator controls. Customer identities stay in your environment and your own confidential environment. [P703-D03] [P703-D04] [HSF1] [HS4] What the lead owner sees Lead Source Web Rating Hot HiveSilo buyer score (custom column) 3,790 of 5,000 HiveSilo qualification (custom column) Tier 1 Note on the lead Open first: strong buying intent on the website Strong buying intent on your website this week. Traffic screened as genuine. Suggested next step: call today. Illustrative example, not a Dynamics 365 screen. Column names are chosen by your administrator. The score shown is HiveSilo's published specimen. [HS8] What HiveSilo sends and the route Dynamics 365 documents Each row below names a route in Microsoft's public documentation for the Dataverse Web API, the API behind Dynamics 365 apps that use the Lead table. HiveSilo calls it outbound to write these rows. In this workflow it does not read lead status or opportunity outcomes back, and it does not ask Dynamics 365 to call into your systems. What HiveSilo writes to Dynamics 365 and the documented route for each item HiveSilo sends Where it lands in Dynamics 365 Documented route A buyer who identifies themselves on your website A row in the Lead table, created or updated PATCH to the leads entity set with alternate key values in the URL. Without an If-Match header, Dataverse treats the request as an upsert. [P703-D04] [P703-D06] A returning visitor who is already your customer The matching row in the Contact table, updated in place The same PATCH upsert on the contacts entity set, addressed by an alternate key. The Contact reference lists Upsert among its messages. Which visitors go to Lead and which to Contact is part of the scope you agree. [P703-D04] [P703-D12] Buyer score and Tier 1, Tier 2 or Tier 3 qualification Lead columns your administrator selects The body of the same upsert. The Lead reference documents Rating (Hot, Warm, Cold), Lead Source and Description; custom columns can be added through EntityDefinitions and its Attributes collection. [P703-D06] [P703-D08] A short reason for the score and a suggested next step A Note related to the lead POST to the annotations entity set, using the subject and notetext properties. The Lead reference documents the Lead_Annotation relationship. [P703-D06] [P703-D07] Campaign and source context Lead Source or columns your administrator selects The body of the same upsert, written to the Lead Source choice column or to custom columns on the Lead table. [P703-D06] [P703-D08] Many scored buyers at once Lead rows, in batches The UpsertMultiple action, which the Lead table lists among its messages. Microsoft advises 100 to 1,000 records per request. [P703-D06] [P703-D09] Access you grant OAuth through Microsoft Entra ID. Your administrator creates an application user in the environment, bound to a registered app, and assigns it a custom security role. Microsoft states that an application user does not consume a paid license. [P703-D02] [P703-D03] Matching key An alternate key on the Lead table holds the identifier HiveSilo uses for matching. A table can have up to ten alternate keys, and Microsoft advises against key values that contain characters such as / or +. [P703-D05] Duplicate detection Dataverse includes default duplicate detection rules for accounts, contacts and leads. Microsoft documents the MSCRM.SuppressDuplicateDetection request header: set to false, a create or update is not completed when a duplicate is found. Your administrator decides whether that header is used. [P703-D18] Limits to plan for Default service protection limits apply per user and per web server: 6,000 requests in a five-minute sliding window, 20 minutes of combined execution time and 52 or more concurrent requests. Dataverse answers 429 with a Retry-After header. Microsoft says these values can change, and entitlement limits are counted separately. [P703-D10] Columns marked deprecated The Lead reference labels msdyn_LeadScore and msdyn_LeadGrade as (Deprecated). Scores are mapped to the standard Rating column or to custom columns your administrator creates, not to those columns. [P703-D06] [P703-D08] How to revoke Your administrator can change the application user's security roles, deactivate it, or delete it once inactive, in the Power Platform admin center. [P703-D03] Where each HiveSilo capability meets Dynamics 365 Each row pairs a published HiveSilo capability with the Dynamics 365 or Dataverse feature it works with. Scope is agreed for each client. The connection writes; any row that needs HiveSilo to read from Dynamics 365 says so and needs a separate privilege from your administrator. Where each HiveSilo capability meets Dynamics 365 HiveSilo capability Dynamics 365 feature it works with What you gain Buyer intelligence and three-tier qualification The Lead and Contact tables: the Rating column on Lead (Hot, Warm, Cold), custom columns, and an alternate key for upsert Sellers see a buyer score and a Tier 1, Tier 2 or Tier 3 qualification on the row they already open, and a returning buyer updates that row instead of adding another. [P703-D05] [P703-D06] [P703-D12] [HSF1] AI firewall, bot defense and site protection Duplicate detection rules for leads, contacts and accounts, applied to Web API writes through the MSCRM.SuppressDuplicateDetection header Invalid traffic is screened before it becomes a lead, and the rows that are written can be held to the duplicate rules you already run. [P703-D18] [HSF1] AdBrain The Lead Source choice column and the Source Campaign lookup on the Lead table Your own Dynamics 365 views and charts can compare sources and campaigns by qualified demand as well as by volume. [P703-D06] [HSF1] Offline conversions, qualified-demand scaling and outcome measurement Lead Status (Open, Qualified, Disqualified), the Qualifying Opportunity lookup, and Opportunity Status (Open, Won, Lost) with Actual Revenue With a read privilege you grant, qualified leads and won opportunities can inform the qualified-buyer feedback sent to supported advertising platforms. [P703-D06] [P703-D14] [HSF1] Revenue Seeker Contact, Account and Opportunity rows already in your environment With a read privilege you grant, Dynamics 365 can be one of the authorized sources searched for revenue opportunities, which go to your own salespeople. HiveSilo cannot see those records. [P703-D12] [P703-D13] [P703-D14] [HSF1] AI Governance & Control The application user, a custom security role with table privileges such as Create, Write, Append and Append To, and Dataverse auditing Every write runs through a user whose privileges your administrator sets and can remove, auditing you turn on can record who created or updated a row and when, and a person decides the outreach. [P703-D03] [P703-D15] [P703-D16] [HS6] Client-controlled privacy and verification Microsoft Entra ID authorization, column-level security, and an environment bound to the geographic location you chose Customer identities stay in your environment, in its geography, and in your confidential environment, outside HiveSilo's visibility. Column-level security can limit who views the score columns. [P703-D02] [P703-D19] [P703-D20] [HS4] [HSF1] How the buying signals are captured and linked Lightweight first-party instrumentation on your own website reads pseudonymous behavior from your visitors, and HiveSilo scores those non-PII signals. Anything that could identify a person goes from your website into your own per-tenant confidential enclave, not into HiveSilo's shared platform. An anonymous session has a score but no row in Dynamics 365. The link is made when the visitor identifies themselves on your website, for example through an enquiry form. That match happens inside your enclave, and the scored Lead or Contact row is written to your environment from there. [HS3] [HS4] What your Dynamics 365 team does The connection is configuration in your environment plus activation on the HiveSilo side. These are the steps on your side, as Microsoft documents them. Register the app. Register an application in Microsoft Entra ID and give it a client secret or a certificate. Microsoft documents this as the way to connect as an app. [P703-D02] Create the application user. In the Power Platform admin center, create an application user for that app in the environment and choose its business unit. One application user is allowed per registered app in an environment. [P703-D03] Assign a narrow security role. Give the application user a custom security role with only the table privileges the agreed writes need: Create and Write on the tables in scope, and Append and Append To so a Note can be attached. [P703-D03] [P703-D15] Add the key and the score columns. Define an alternate key on the Lead table, and on Contact if it is in scope, and choose or create the columns that hold the score, tier and source context. [P703-D05] [P703-D08] Test in a sandbox environment first. Microsoft describes a sandbox environment as non-production, isolated from production, and the place to test changes with low risk. Check column mapping, the alternate key and your duplicate rules there. [P703-D17] [P703-D18] Decide on auditing. If you want a record of each write, turn on Dataverse auditing for the environment, the table and the columns in scope, and select a retention period. [P703-D16] Switch on production. Create the application user and assign the same role in your production environment once the sandbox result is accepted. [P703-D03] HiveSilo's published typical deployment is approximately 72 hours to set up and 7 days to live mapping and go-live, subject to fit, customer readiness and agreed scope. The Dynamics 365 steps above run on your own change process. [HSF1] Who, what, when, where, how and why Who Organizations that work leads in Dynamics 365 and want sellers to see buying intent from the company website. A Power Platform administrator creates the application user and its security role. [P703-D03] What A buyer score, a Tier 1, Tier 2 or Tier 3 qualification, a short reason for them, a suggested next step and campaign context, written to the Lead or Contact row and to a related Note. [P703-D06] [P703-D07] [P703-D12] When When a visitor identifies themselves on your website, for example through an enquiry form, and again when a returning buyer's score changes. [HS1] Where In your own Dynamics 365 environment, on the lead your sellers already open. Your team does not have to check a second customer database. [P703-D04] [HS4] How Outbound HTTPS calls to the Dataverse Web API, an OData version 4.0 service, authorized by Microsoft Entra ID and matched on an alternate key. [P703-D01] [P703-D02] [P703-D04] Why Dynamics 365 holds the relationship and the sales process. HiveSilo observes how the buyer behaved on your website before the enquiry. The seller reads both on one row. [HS1] [HS2] See the intelligence behind the next move One lead per buyer, kept current. HiveSilo sends a PATCH request addressed by an alternate key on the leads entity set. Microsoft documents that this request creates the row when no match exists and updates it when one does. [P703-D04] [P703-D05] [P703-D06] Useful output: A single lead row per buyer, carrying the latest score and tier. The explanation, as a note on the lead. A short reason for the score and the suggested next step are posted as a Note, the annotation table in Dataverse, related to the lead through the documented Lead_Annotation relationship. [P703-D06] [P703-D07] Useful output: A note on the lead timeline that explains the score. Columns you own and can report on. Score and tier land in columns your administrator selects or creates. The standard Rating column offers Hot, Warm and Cold, and custom columns can be added to the Lead table for numeric values. [P703-D06] [P703-D08] [HS1] Useful output: Lead columns your own views, charts and flows can read. Two new leads before the morning stand-up. Illustrative workflow: two leads reach Dynamics 365 overnight. Both carry a topic and a company name. One shows strong buying intent and is qualified Tier 1; the other shows little and is Tier 3. Start with Microsoft Dynamics 365 Dynamics 365 creates both leads and applies the assignment and rating rules you have configured. That process is unchanged. Bring the relevant context together Each lead as Dynamics 365 created it, with its owner and lead source. HiveSilo's score and tier for the website sessions behind each enquiry. A short reason for each score, including any invalid-traffic concern. Make the decision The seller opens the Tier 1 buyer first and handles the second lead according to its lower score. A useful output A lead row whose columns show the score and tier, with a Note that explains them. Keep responsibility clear The lead owner in Dynamics 365 decides the outreach. HiveSilo supplies evidence; it does not contact the buyer in this workflow. Hold and ask Hold automated outreach when the score is low, the traffic-quality concern is unresolved or contact permission is unclear. Record the outcome Qualify or disqualify the lead in Dynamics 365 as usual. Your own views and reports can then compare the score column with the outcome. HiveSilo does not read that outcome back in this workflow. [P703-D06] [P703-D07] Require control before AI acts. A score is advice to the seller. The seller and your rules still decide. Agree which Dynamics 365 actions a score may drive and which need a person. Writing a column is different from reassigning a lead or starting a sequence. Give the application user a security role that covers only the tables and columns in scope, and keep any automation that reads the score under your own administrator's control. 1 Request An AI proposes an action 2 Check Policy and authority 3 Approve Named owner, when required 4 Act Within permitted scope 5 Record Keep the action, outcome and accountable owner traceable. Unclear authority? Hold the action. Resolve with the named, authorized owner before proceeding. Controls apply to actions routed through the configured HiveSilo boundary. Read the governance and escalation requirements Make accountable authorization a condition of putting AI to work. HiveSilo describes an operating layer that combines buyer intelligence, customer-data privacy and governance. Your deployment should establish the responsible owner and permitted scope before an agent can change records, contact buyers or trigger campaigns. HiveSilo documents policy checks before execution, default denial when authorization is unclear, human checkpoints, scoped stop controls and decision receipts. These controls apply to actions routed through its policy boundary. Keep decisions, required approvals and held actions traceable as the workflow progresses, then record the action, outcome and accountable owner. [HS6] [HS7] Who Identify the acting agent or person and name the business owner accountable for this workflow. What Define the action and permitted data categories before execution. Where Specify the approved system, destination and customer custody boundary. How Require an approved execution path, access scope and applicable policy checks. When Set the permitted conditions and approval validity; recheck authority before a held action resumes. Why Record the business purpose and the basis for allowing, denying or holding the action. An edge case should stop the affected action. For the deployment, require unresolved authority, an unapproved destination or an out-of-policy action to remain on hold. A timeout or unanswered approval request must not become permission to proceed. Who gets the question? Agree a named owner and authorized delegate for each workflow. A proposed responsibility model is: sales for buyer outreach and lead handling; marketing for campaign spend and audiences; security or privacy for data-access exceptions; the platform owner for connector or runtime changes. Test the escalation route. If no authorized reviewer is available, keep the action held. Named-owner routing is configured and demonstrated for each deployment. Governance covers actions routed through its configured boundary; external systems remain responsible for actions outside that scope. Make responsibility part of the AI rollout. Use the AI implementation layer to put policy checks, approval checkpoints and decision records around the actions in scope. Your enterprise agreement defines the legal responsibilities and any agreed liability allocation or transfer. [HS7] [HS10] Explore the AI implementation layer · How enterprise agreements govern the engagement Your client list stays yours. Your leads stay in your Dynamics 365 environment. Explore the security architecture Your client records stay with your business under HiveSilo’s published architecture. How your data stays under your control The lead's identity is written to your own Dynamics 365 environment from the environment you control. HiveSilo's shared platform receives permitted non-PII signals and scores. The application user's security role and Dynamics 365 security continue to govern what is written and who can read it. [P703-D02] [P703-D03] [HS3] [HS4] [HS4] Your controlled environment Customer identities stay in your Dynamics 365 environment Identities and re-identifiable records stay here. Your enclave. Your keys. Only permitted non-PII signals and scores Permitted non-PII website signals and buyer scores HiveSilo intelligence HiveSilo: buyer score, tier and reasons No customer identity transfer to HiveSilo. Published architecture. Confirm the data boundary for your deployment. Customer-controlled keys Documented BYOK options cover AWS, Azure and GCP. Review key ownership, revocation and the deployment's access policy with your security team. [HS3] Protected processing The architecture describes confidential computing and trusted execution environments. Request deployment-specific attestation and data-flow evidence for your CISO's review. [HS3] Scoped destinations and actions Agree which systems receive outputs and what actions are authorized. Keep identity handling within the documented customer boundary. [HS2] [HS4] Control through the full relationship Review permitted use, export, retention, deletion and offboarding terms. Customer-controlled keys are one control; they do not establish every contractual exit right. [HS3] [HS4] The lead's identity is written to your own Dynamics 365 environment from the environment you control. HiveSilo's shared platform works with permitted non-PII signals and scores. The security role your administrator assigns limits what the application user can write, and Dynamics 365 security continues to govern who can read it. A Microsoft Dynamics 365 review of the connection should confirm the application user's security role and the columns it may write. [P703-D02] [P703-D03] [HS3] [HS4] Customer identity custody is separate from HiveSilo account, billing and support records. Re-identifiable pseudonymous data is not anonymous. What you could gain. Bring website buying evidence to the Dynamics 365 lead, so prioritization, the first call and the source review all draw on the same facts. Explore HiveSilo case studies Contact HiveSilo Select a benefit to explore Pause rotation Buyer scoring Scale winners Less waste Bot protection Find revenue 3,790 of 5,000 · UHNW buyer score 3 , 7 9 0 of 5,000 Illustrative score 4–6× · Reported conversion lift 4 – 6 × Closed-revenue outcomes Up to 31% · Reported ad-spend savings Up to 3 1 % Bot and invalid-traffic filtering 99.9999% · Bot detection 9 9 . 9 9 9 9 % Observed client results 5–21% · Revenue lift from existing data 5 – 2 1 % HiveSilo-reported client results Sharper scoring. Clearer intent. 3,790 of 5,000 · UHNW buyer score Illustrative score Sort new Dynamics 365 leads by observed buying intent before a seller opens them. Find more clients like your best. 4–6× · Reported conversion lift Closed-revenue outcomes See which sources and pages your best-scoring Dynamics 365 leads share, then invest more there. Put more of your budget to work. Up to 31% · Reported ad-spend savings Bot and invalid-traffic filtering Question spend on sources whose leads score low and seldom qualify. Keep evolving your protection. 99.9999% · Bot detection Observed client results Screen invalid traffic before it becomes a lead in a seller's queue. Goal, not an achieved result: toward 99.9999999% bot detection as the hive evolves. Observed client results vary. Find revenue in data you already own. 5–21% · Revenue lift from existing data HiveSilo-reported client results Find open Dynamics 365 leads whose owners have gone quiet while the buyer shows renewed buying intent on your website. Published outcomes include client-reported results and illustrative, unaudited ranges. The owned-data revenue range was supplied by HiveSilo; request the measurement context in your briefing. Results vary. Measure what matters Define the result. Then require the evidence. Focus on better-directed follow-up, less acquisition waste, protected customer identity custody and accountable AI execution. Agree the baseline, success measures and scope for your business. CEO: a clearer decision about the opportunities that merit attention. CFO: an agreed baseline, evaluation costs and attributable outcomes before any ROI claim. CTO: a demonstrated, permitted connection and a usable handoff into the agreed system. CISO: verified identity custody and pre-action authorization, with tested hold, approval and revocation behavior. Explore HiveSilo’s published outcomes and the measurement context behind them. [HS5] [HS8] [HS9] Make your next conversation count. Bring your Microsoft Dynamics 365 workflow. Map the decision, the data you control and a measurable next step with HiveSilo. Enterprise CRM & customer data · Sales, marketing operations, technology & security Contact HiveSilo Mention Microsoft Dynamics 365 and your business question. No client records or credentials. A closer look, when you need it. Product scope, a practical workflow and source-backed answers for your team and its research tools. Read fact sheet Structured JSON RSS updates Reviewed November 2026 Contact HiveSilo Microsoft Dynamics 365 connection & briefing scope Agree the environment, the key and the security role. Confirm the Dynamics 365 environment URL, the alternate key used for matching, and the Lead columns that will hold the score, tier and source context. Your administrator registers the app in Microsoft Entra ID, creates the application user and assigns a security role limited to those writes. The connection is available and is activated for each client on request. Microsoft's documentation establishes what the Dataverse Web API supports; your environment's configuration, your agreements with Microsoft and your agreement with HiveSilo determine the scope that is switched on. When you review Microsoft Dynamics 365 with HiveSilo, ask which seller decision a website buyer score would change. [P703-D02] [P703-D03] [HS3] [HS4] [P703-D02] [P703-D03] [P703-D05] [HS10] A useful fit when Most useful where Dynamics 365 is the system of record for leads and the website is a material source of them. Sales teams that work the Lead table in Dynamics 365 every day. Businesses with considered, high-value purchases where the order of follow-up matters. Organizations with a Power Platform administrator who can create an application user, a security role and an alternate key. Consider the fit The rating, assignment and automation features already in Dynamics 365 may answer the question for some teams. An alternate key on the Lead table has to exist before upserts can match on it. Service protection limits apply per user, so plan volume with your administrator. In your enquiry, name Microsoft Dynamics 365 and the business decision. Please leave out client records, credentials and sensitive samples. Eight questions before your briefing 1. Does HiveSilo connect to Microsoft Dynamics 365? Yes. The Dynamics 365 connection is available and is activated for each client on request. It uses the Dataverse Web API that Microsoft documents, with access your administrator grants. [P703-D01] [HS2] 2. Which Dynamics 365 tables does HiveSilo write to? The Lead table for new buyers and the Contact table for visitors who are already your customers, both by upsert on an alternate key, plus a Note (annotation) for the explanation and next step. Other tables, including Account, Opportunity and custom tables, are scoped for each client through the same Web API. Your administrator selects the columns. [P703-D04] [P703-D06] [P703-D07] [P703-D12] [P703-D13] 3. Will it create duplicate leads? The write is an upsert addressed by an alternate key. Microsoft documents that the request updates the matching row and creates one only when no row matches. Matching depends on the alternate key your administrator defines. [P703-D04] [P703-D05] 4. Does the integration need a paid user license? Microsoft's documentation says a server-to-server integration connects as an application user bound to a registered app, and that this approach does not consume a paid license. Your own licensing terms with Microsoft still apply. [P703-D02] [P703-D03] 5. How is access granted and removed, and can we test first? Your administrator registers an app in Microsoft Entra ID, creates an application user for it in the environment and assigns a security role. They can change the roles, deactivate the user or delete it once inactive. Microsoft documents sandbox environments, isolated from production, for testing, and the connection can be pointed at a sandbox first. [P703-D02] [P703-D03] [P703-D17] 6. Does HiveSilo read data back from Dynamics 365? Not in this workflow. HiveSilo writes the score, tier and explanation; comparing score with outcome happens in your own views and reports. Reading outcomes back would need a separate Read privilege on the security role, which you would have to grant. Each write counts toward the service protection limits, 6,000 requests per user in a five-minute sliding window by default, and Dataverse answers 429 with a Retry-After header when a limit is reached. [P703-D10] [P703-D15] 7. Does Dynamics 365 already rate leads? Yes. The Lead table has a standard Rating column with Hot, Warm and Cold, and Dynamics 365 offers its own assignment and automation. HiveSilo adds first-party evidence from your own website, including traffic-quality screening, to the same lead. [P703-D06] [HS1] 8. Is HiveSilo listed on Microsoft Marketplace? No listing is claimed. Microsoft documents a Partner Center submission process for apps listed on its Marketplace. This connection is set up directly in your environment with an application user your administrator creates. [P703-D11] Sources, scope & verification Microsoft Learn: Use the Microsoft Dataverse Web API [P703-D01] The Dataverse Web API implements OData version 4.0 and can be called from any language that sends authenticated HTTP requests. Reviewed November 2026 Microsoft Learn: Use OAuth authentication with Microsoft Dataverse [P703-D02] Web API clients must use OAuth with Microsoft Entra ID as the identity provider; a server-to-server client connects as an application user bound to a registered app, using a client secret or certificate and the scope <environment-url>/.default, and that user does not consume a paid license. Reviewed November 2026 Microsoft Learn: Manage application users in the Power Platform admin center [P703-D03] An administrator creates an unlicensed application user in an environment, assigns its business unit and security roles, and can edit those roles, deactivate the user or delete it once inactive; one application user per registered Microsoft Entra application per environment. Reviewed November 2026 Microsoft Learn: Use Upsert to Create or Update a record [P703-D04] A PATCH request to an entity set with key values in the URL is an upsert unless the If-Match: * header is sent; it creates the record when none matches and returns 204 No Content either way, or 201 and 200 with Prefer: return=representation; alternate keys are the expected way to identify records in data integration. Reviewed November 2026 Microsoft Learn: Work with alternate keys [P703-D05] An alternate key lets a Dataverse column hold the unique identifier used by an external system; a table can have up to ten alternate key definitions, and key values containing certain characters such as / or + stop GET and PATCH by key from working. Reviewed November 2026 Microsoft Learn: Lead table/entity reference (Microsoft Dynamics 365) [P703-D06] The Lead table has EntitySetName leads and supports the Create, Update, Upsert and UpsertMultiple messages; columns include Subject, CompanyName, EMailAddress1, Description, LeadSourceCode and LeadQualityCode (display name Rating, choices Hot, Warm and Cold); the msdyn_LeadScore and msdyn_LeadGrade columns carry display names marked (Deprecated); the Lead_Annotation relationship links notes to a lead. The same page documents the Status column (Open, Qualified, Disqualified), the Qualifying Opportunity lookup, the Source Campaign lookup and the Web choice of Lead Source. Reviewed November 2026 Microsoft Learn: annotation EntityType (Dataverse Web API reference) [P703-D07] The annotation entity has display name Note, entity set path [organization URI]/api/data/v9.2/annotations, supports POST, GET, PATCH and DELETE, and carries the subject and notetext properties. Reviewed November 2026 Microsoft Learn: Create and update column definitions using the Web API [P703-D08] Columns can be added to an existing table with a POST to EntityDefinitions(LogicalName='<table>')/Attributes; documented examples include string, integer, decimal, memo and choice columns. Reviewed November 2026 Microsoft Learn: Use bulk operation messages [P703-D09] The UpsertMultiple action performs upserts in bulk, identifying records by alternate key, and returns 204 No Content; Microsoft advises sending 100 to 1,000 records at a time; two records with the same key in one payload return an error. Reviewed November 2026 Microsoft Learn: Service protection API limits [P703-D10] Default limits per user and per web server: 6,000 requests within a five-minute sliding window, 20 minutes of combined execution time in that window, and 52 or more concurrent requests; the Web API returns 429 Too Many Requests with a Retry-After header; the values can change and vary by environment; entitlement limits are evaluated separately. Reviewed November 2026 Microsoft Learn: Publish your app on Marketplace [P703-D11] Listing an app on Microsoft Marketplace requires a Microsoft Partner Center account, a managed solution and a Marketplace package submitted through Partner Center. HiveSilo does not claim a marketplace listing. Reviewed November 2026 Microsoft Learn: Contact table/entity reference (Microsoft Dataverse) [P703-D12] The Contact table is described as a person with whom a business unit has a relationship, such as customer, supplier, and colleague; its EntitySetName is contacts; it supports the Create, Update, Upsert and UpsertMultiple messages; the Contact_Annotation relationship links notes to a contact. Reviewed November 2026 Microsoft Learn: Account table/entity reference (Microsoft Dataverse) [P703-D13] The Account table is described as a business that represents a customer or potential customer; its EntitySetName is accounts; it supports the Create, Update, Upsert and UpsertMultiple messages and carries an Account Rating choice column. Reviewed November 2026 Microsoft Learn: Opportunity table/entity reference (Microsoft Dynamics 365) [P703-D14] The Opportunity table is described as a potential revenue-generating event, or sale to an account; its EntitySetName is opportunities; columns include Rating (Hot, Warm, Cold), Originating Lead, Status (Open, Won, Lost), Est. revenue, Actual Revenue and Actual Close Date. Reviewed November 2026 Microsoft Learn: Security roles and privileges for Dataverse [P703-D15] Security roles define how users access records; table privileges include Read, Create, Delete, Write, Assign, Share, Append and Append To, each with an access level; privileges from several roles are cumulative; Append To on a record is what allows a note to be added to it. Reviewed November 2026 Microsoft Learn: Manage Dataverse auditing [P703-D16] Dataverse auditing logs changes to customer records, including create, update and delete operations, and helps answer who created or updated a record and when and which fields changed; it is configured at environment, table and column level, with a retention period the administrator selects. Reviewed November 2026 Microsoft Learn: Sandbox environments [P703-D17] A sandbox environment is any non-production environment of Microsoft Dataverse, isolated from production, described as the place to develop and test application changes with low risk; it is managed in the Power Platform admin center. Reviewed November 2026 Microsoft Learn: Detect duplicate data using the Web API [P703-D18] The MSCRM.SuppressDuplicateDetection request header, set to false, stops a Web API create or update when a duplicate is found; Dataverse includes default duplicate detection rules for accounts, contacts and leads; duplicate detection is suppressed by default when updating through the Web API. Reviewed November 2026 Microsoft Learn: Column-level security [P703-D19] Column-level security can prevent certain users from setting the value of a column or viewing its data; the configuration is organization-wide, applies to all data access requests and needs the system administrator role to set up. Reviewed November 2026 Microsoft Learn: Power Platform environments overview [P703-D20] Each environment is created under a Microsoft Entra tenant and is bound to a geographic location; the environment types include Production and Sandbox, and sandbox environments are used for development and testing, separate from production. Reviewed November 2026 HiveSilo capability overview [HSF1] Published HiveSilo capabilities: buyer intelligence with Tier 1, Tier 2 and Tier 3 qualification, Revenue Seeker, AdBrain, offline conversion feedback and outcome measurement, AI Governance & Control, bot defense and client-controlled privacy; typical deployment of approximately 72 hours to set up and 7 days to live mapping and go-live, subject to fit, customer readiness and agreed scope. Reviewed November 2026 HiveSilo: industry coverage [HS0] First-party description of buyer intelligence across 12 luxury niches. Reviewed October 2026 HiveSilo: platform [HS1] Published intent, sales-prioritization and traffic-quality capabilities. Reviewed October 2026 HiveSilo: integration scope [HS2] Named destinations, scoped activation and customer-controlled dispatch. Reviewed October 2026 HiveSilo: security architecture [HS3] Documented confidential processing, BYOK and customer control. Reviewed October 2026 HiveSilo: data handling [HS4] Customer identity custody, pseudonymous-data boundaries and separate account records. Reviewed October 2026 HiveSilo: published outcomes [HS5] Existing first-party outcomes material, with client-reported and illustrative descriptions. Reviewed October 2026 HiveSilo: AI agentic governance [HS6] Published pre-action policy checks, default denial, human checkpoints, scoped stop controls and governance receipts. Reviewed October 2026 HiveSilo: AI implementation layer [HS7] Published combined implementation model for intelligence, confidential processing and AI governance. Reviewed October 2026 HiveSilo: bot-detection results and buyer-score specimen [HS8] The homepage presents 99.9999% bot detection as observed client results, 99.9999999% as a goal, and a 3,790-of-5,000 UHNW buyer-score specimen. Reviewed October 2026 HiveSilo: owned-data revenue result briefing [HS9] HiveSilo supplied a 5–21% client revenue increase range for existing-data workflows in October 2026. Reviewed October 2026 HiveSilo: enterprise agreements and responsibility [HS10] Signed enterprise agreements govern the engagement and take precedence over website summaries. Reviewed October 2026 Vendor sources describe their own product. The workflows on this page describe a HiveSilo application, scoped to customer permissions, contracts and the selected product edition. HiveSilo’s reported outcomes retain their original measurement context; the illustrative score and future bot-detection goal are identified in the outcomes section. Independent HiveSilo use-case page. Microsoft Dynamics 365 is identified to explain the workflow; no endorsement, certification or partnership is implied. Your next move starts with a conversation. Contact HiveSilo"
}
