Streamline Location-Specific Policies with SharePoint and Amazon Bedrock
Global companies often face challenges in providing employees with location-specific policies. For instance, leave policies in the USA differ significantly from those in India. However, when documents are stored together in systems like SharePoint without proper filtering, employees may waste time searching or risk following incorrect policies. This issue also impacts knowledge bases like Amazon Bedrock, where unfiltered content leads to inaccurate answers.
The Solution: Metadata Filtering with SharePoint and Amazon Bedrock
By integrating Amazon Bedrock Knowledge Bases with SharePoint and leveraging metadata filtering, companies can create intelligent Retrieval-Augmented Generation (RAG) systems. These systems automatically retrieve relevant policy documents based on location filters, ensuring employees receive accurate, location-specific information.
How It Works (In Simple Terms)
- Organize Documents in SharePoint: Assign metadata (e.g., country-specific tags) to each document.
- Connect SharePoint to Amazon Bedrock: Sync SharePoint as a data source for Amazon Bedrock Knowledge Bases.
- Apply Metadata Filters: Use filters to retrieve only location-relevant content when employees query the system.
Real-World Example: Leave Policies
Consider leave policies for the USA and India:
- USA Policy: Based on ACME Corporation’s USA Employee Leave Policy, employees receive different types of leave: Vacation Leave (0-2 years of service: 10 days/80 hours), Sick Leave - 5 days (40 hours) per calendar year. Additionally, employees receive paid holidays (11 days), bereavement leave, and jury duty leave. Eligible employees may receive up to 12 weeks for parental leave.
- India Policy: According to ACME Corporation India’s leave policy, you are entitled to the following types of leave: Privilege/Earned Leave: 24 days per year, Sick/Casual Leave: 12 days per calendar year. Optional Holidays: 2 days per year. The policy includes other types of leave such as Maternity Leave: 26 weeks.
Disclaimer: Please note that the leave policies uploaded to SharePoint and used in this demonstration were generated using AI. These AI-generated policies are intended for illustrative purposes only.
Using metadata filtering:
- Employees in the USA see only the USA policy.
- Employees in India see only the India policy.
This eliminates confusion and ensures compliance.
Implementation Steps
Add metadata to your SharePoint documents
First, ensure your documents have the right metadata in SharePoint:
- We will use the default Title column in your SharePoint document library
- Assign “Leave_Policy_USA” or “Leave_Policy_India” to the appropriate documents

Set up a connection between SharePoint and Amazon Bedrock
Next, set up a connection between SharePoint and Amazon Bedrock:
- In AWS console, create a new Knowledge Base
- Select SharePoint as your data source
- Set up SharePoint App-Only authentication to connect to SharePoint
- Sync the data source to begin indexing content from SharePoint



Note: I’m still exploring how custom metadata columns can be used for unstructured data formats. If I find a solution, I’ll create a separate blog post. For now, we’ll focus on using the out-of-the-box metadata fields generated by the OpenSearch collection.
Test metadata filtering using sample queries to ensure accuracy
Let us test a few questions both with and without filters to see how the selected model generates responses. This will help demonstrate the difference in relevance and accuracy when metadata filtering is used. For this example, I’ve used the Nova Pro 1.0 model to generate the responses.
No Filter
As you can see, the answers are a mix of both USA and India policies, with chunks being pulled from documents for both regions.

With x-amz-bedrock-kb-title ^ Leave_Policy_USA Filter
With the filter x-amz-bedrock-kb-title ^ Leave_Policy_USA, the response is clearly specific to the USA, showing only the relevant policy for that region.

With x-amz-bedrock-kb-title ^ Leave_Policy_India Filter
With the filter x-amz-bedrock-kb-title ^ Leave_Policy_India, the response is clearly specific to the India, showing only the relevant policy for that region.

Benefits of Metadata Filtering
- Accurate Information: Employees access policies specific to their region.
- Time-Saving: Reduces time spent sifting through irrelevant documents.
- Improved Compliance: Ensures employees follow the correct policies.
- Centralized Management: All policies remain in one system for easy updates.
Conclusion
Combining SharePoint’s document management capabilities with Amazon Bedrock’s metadata filtering creates a powerful solution for global organizations. This approach simplifies policy management and ensures employees receive accurate, location-specific information without requiring complex coding or major system changes.
Published on:
Learn moreRelated posts
SharePoint Framework (SPFx) roadmap update – December 2025
SPFx is powering the future of Microsoft 365. From AI-driven portals to seamless integrations across SharePoint, Teams and Viva, SPFx is drivi...
Exam AB-900: Microsoft 365 Copilot and Agent Administration Fundamentals
Following on the steps of the other AB exams I’ve been writing about my experience with (see Exam AB-730: AI Business Professional &...
Microsoft Copilot (Microsoft 365): Chat History Landing page: Filtering UI Refresh
To help you quickly find the conversations that matter, we’re updating the Chat History filtering experience. This refresh makes the interface...
Microsoft Copilot (Microsoft 365): Capture voice notes in the Microsoft 365 Copilot mobile app
With a Microsoft 365 Copilot license, transform offline discussions into structured, actionable, and searchable content with voice notes in Co...
Microsoft Graph PowerShell SDK V2.34 Makes WAM the Default
The Web Account Manager (WAM) authentication broker becomes the default method for handling interactive Microsoft Graph PowerShell SDK connect...
Microsoft 365: New functionality and prices in 2026
A range of security and AI enhancements have been announced for the Microsoft 365 suite of products in 2026, along with some small price incre...
Automating Microsoft 365 with PowerShell Update 19
Update #19 of the Automating Microsoft 365 with PowerShell eBook is now available. Subscribers can download the updated PDF and EPUB files fro...
Teams admin center: Auto‑updates for Teams Android device firmware and apps will be paused during year‑end holidays
Auto-updates for Teams Android device firmware and apps via Teams admin center will pause from December 20, 2025, to January 12, 2026, to ensu...
OpenAI’s GPT-Image-1.5 model is now available in Microsoft 365 Copilot
Microsoft 365 Copilot will replace GPT-4o with OpenAI’s GPT-Image-1.5 from mid-December 2025 to late January 2026, enhancing image generation ...
Teams admin center: Messaging safety defaults changing to “On” by default
Starting January 12, 2026, Microsoft Teams will enable messaging safety features by default, including weaponizable file type protection, mali...