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 with the Provider. This implementation matches the use case demonstrated in the image below. The code has been segmented to represent a Customer's infr
active 2023-10-18 → 2025-01-21 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 462 days from 2023-10-18 to 2025-01-21. Pushes: 2 total, peak 1 in a day. Pull requests: 1 total, peak 1 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
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| mikeyqin | 1 | 0 | 0 | 0 |
| aulong-msft | 1 | 1 | 0 | 0 |
| dependabot[bot] | 1 | 0 | 1 | 0 |
| ashtmMSFT | 1 | 1 | 0 | 0 |
Recent activity
Latest issues, pull requests and releases
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.