关于Azure Bot Service for B2B跨O365租户日程助理机器人可行性咨询

Hey Madhan, this scenario is absolutely feasible using Microsoft 365's built-in B2B collaboration capabilities and the Microsoft Graph API. Let’s walk through how to make this work, plus key considerations and alternatives if you hit any roadblocks.

Prerequisites First #

Before building the bot, you’ll need to set up the foundational B2B access:

• Ensure Tenant2 and Tenant3 have enabled external B2B collaboration (this is enabled by default in most tenants, but double-check via the Azure AD admin center).
• User2@def.com and User3@ghi.com need to grant appropriate calendar permissions to User1@abc.com, or your tenant admins can configure tenant-wide calendar sharing settings to allow external users to view free/busy details (or full calendar info, depending on your needs).

Core Implementation with Microsoft Graph API #

Your bot will rely on two key Graph API endpoints to achieve this workflow:

1. Fetch Free/Busy Time Slots #

Use the getSchedule endpoint to retrieve available time for User2 and User3 across tenants:

POST https://graph.microsoft.com/v1.0/users/{user-id}/calendar/getSchedule
Content-Type: application/json

{
  "schedules": ["user2@def.com", "user3@ghi.com"],
  "startTime": {
    "dateTime": "2024-06-01T09:00:00",
    "timeZone": "Pacific Standard Time"
  },
  "endTime": {
    "dateTime": "2024-06-01T17:00:00",
    "timeZone": "Pacific Standard Time"
  },
  "availabilityViewInterval": 30
}

• Required permissions: For delegated access (acting as User1), use Calendars.Read; for application-level access (bot acting on its own), use Calendars.Read (needs admin consent in each target tenant).

2. Book the Shared Calendar Event #

Once you’ve identified overlapping available slots, create an event and invite User2 and User3 using the events endpoint:

POST https://graph.microsoft.com/v1.0/users/{user1-id}/calendar/events
Content-Type: application/json

{
  "subject": "Cross-Tenant Project Sync",
  "start": {
    "dateTime": "2024-06-01T10:00:00",
    "timeZone": "Pacific Standard Time"
  },
  "end": {
    "dateTime": "2024-06-01T11:00:00",
    "timeZone": "Pacific Standard Time"
  },
  "attendees": [
    {
      "emailAddress": {
        "address": "user2@def.com",
        "name": "User2"
      },
      "type": "required"
    },
    {
      "emailAddress": {
        "address": "user3@ghi.com",
        "name": "User3"
      },
      "type": "required"
    }
  ]
}

• Required permissions: Delegated access uses Calendars.ReadWrite (User1 can create events in their own calendar and invite external users); application access uses Calendars.ReadWrite.

Key Considerations to Avoid Issues #

• Calendar Sharing Limits: By default, external B2B users might only see free/busy info without details. Adjust this in the Exchange Admin Center (Settings > Sharing > Calendar sharing) for Tenant2 and Tenant3 if you need more visibility.
• Cross-Tenant App Permissions: If using an application-level bot, you’ll need to set up cross-tenant access policies in Azure AD to allow your bot’s service principal to access resources in Tenant2 and Tenant3.
• Conflict Handling: Build logic to check for last-minute schedule changes before booking, as cross-tenant sync can have minor delays.

Alternative Workflows (If Graph API Isn’t Ideal) #

If you prefer a low-code approach or hit permission barriers:

• Microsoft Teams Meetings: User1 can directly invite User2 and User3 (as external contacts) to a Teams meeting; Teams automatically checks their free/busy time and sends calendar invites.
• Power Automate: Build a flow that triggers on a user request, queries free/busy slots via Graph, and creates the event—no custom code needed.

内容的提问来源于stack exchange，提问作者madhantce