Dynamics365_Integration_Boundary_Reference_v2.pdf
PDF 354 KB Posted
- Attached to
- Citywide Operational Technology Taxonomy
- Solicitation number
- PE-66062-NONST-2026-000000293
- Issued by
- Fulton County, Atlanta City, Georgia
About this file
This document is a Microsoft Dynamics 365 Integration Boundary Reference guide prepared as an internal reference for the City of Atlanta's upcoming Citywide Operational Technology Taxonomy procurement. The City of Atlanta is undertaking a multi-step competitive sealed bid process to procure enterprise technology and operational taxonomy services with a core focus on Customer Relationship Management (CRM) systems. The selected vendor will be responsible for translating the City's organizational strategies into comprehensive enterprise architecture deliverables, including future state conceptual architecture, roadmap, and taxonomy documentation. A pre-solicitation conference will be noticed and held to provide additional details and address prospective bidders' questions regarding the specific requirements to be outlined in the pre-qualification document.
The reference guide details critical integration boundaries and constraints for Microsoft Dynamics 365 cloud environments that vendors must consider during implementation. Key constraints include API rate limits (6,000 requests per 5 minutes with 52 concurrent connections), maximum file attachment sizes of 128 MB via Web API, bulk import limitations for records exceeding 100,000 or payloads over 32 MB, and authentication requirements via OAuth 2.0 through Azure Active Directory. Additional considerations include licensing entitlements for per-user API calls, database and storage capacity quotas, and recommended tools such as Azure Data Factory, Synapse Link, or Dataflows for large data transfers. Vendors must account for these technical constraints when designing integration solutions and may need to recommend additional Power Platform capacity or external storage solutions to meet the City's operational requirements.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Updated_Pre_Advertising_Notice_Template_11_25.pdf | ||
| COA_ArialFont_UsageGuide.pdf | ||
| Citywide Operational Taxonomy _ Quantified Qu.docx | DOCX document | |
| CoA_Brand Guide_QuickGuide.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Microsoft Dynamics 365 (Cloud) – Integration Boundary Reference
Executive / PMO Summary
This document outlines the known boundaries, constraints, and reference guidelines when integrating with Microsoft Dynamics 365 (Customer Engagement / Dataverse) cloud environments. It is intended to inform program and project management teams overseeing integration workstreams and vendor engagements.
Key Integration Boundaries
Category Boundary / Constraint Summary Impact
API Limits & Throttling
Service Protection API limits (6,000 requests / 5 min; 52 concurrent; 600s total execution)
Integrations may be throttled if limits are exceeded.
Use batching, retry logic, or multiple service accounts.
Licensing Entitlements
Per-user API call entitlements per day
High-volume integrations may exceed licensed capacity; additional Power Platform capacity may be required.
Data Volume Bulk imports >100K records or 32MB payloads may fail
Use Azure Data Factory, Synapse Link, or Dataflows for large data transfers.
File/Attachment Size Max 128 MB via Web API Larger files must be stored externally (SharePoint or Blob Storage).
Authentication OAuth 2.0 via Azure AD required All integrations must use an Application User with client secret or certificate for authentication.
Storage Capacity Database, file, and log capacity quotas enforced
Heavy integrations can quickly consume capacity;
monitor usage and archive regularly.
Reference Links (Microsoft Documentation)
• Service protection API limits: https://learn.microsoft.com/power-apps/developer/data-platform/api-limits
• Dataverse change tracking: https://learn.microsoft.com/en-us/power-apps/developer/data-platform/use-change-tracking-synchronize-data-external-systems
• Azure Service Bus integration: https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-messaging-overview
• OAuth authentication: https://learn.microsoft.com/en-us/power-apps/developer/data-platform/authenticate-oauth
• Plugin & workflow limits: https://learn.microsoft.com/power-apps/developer/data-platform/best-practices/business-logic
© 2025 – Internal Reference Use Only
File details come from the government source that posted it. Updated .