Skip to content

Azure-Samples/Cross-Tenant-Communication-Using-Azure-Service-Bus

View on GitHub ↗Related repositories →

This PoC contains a sample solution for handling cross-tenant communication between a Provider and one or more of its Customers using Service Bus message queues with Azure AD Identities. The problem is of a multi-tenanted nature: the Provider needs to communicate securely with each of its Customers, and each Customer needs to communicate securely w

active 2024-04-262025-01-21 (UTC)

Partial coverage24,918 / 26,318 hourly files (95%) · 2 absent upstream · 1,399 failed, retryable2023-08-152026-08-15 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
17
Pushes
2
Pull requests
0
Issues
1
Stars
4
Forks
10

Activity over time

Daily event counts in the loaded window

Line chart, 271 days from 2024-04-26 to 2025-01-21. Pushes: 2 total, peak 1 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 1 total, peak 1 in a day. Comments: 0 total, peak 0 in a day. Stars: 4 total, peak 1 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
mikeyqin1000
aulong-msft1100
ashtmMSFT1100

Recent activity

Latest issues, pull requests and releases

  • Issue#8mikeyqin2025-01-07 23:59
    Question: URLs for tenants in Azure China

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 4 stars here means stars gained during the window, not the repo's star count.