Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question: azure sdk docs/resources for multi-tenancy apps #7977

Open
jeremysimmons opened this issue Sep 12, 2024 · 0 comments
Open

Question: azure sdk docs/resources for multi-tenancy apps #7977

jeremysimmons opened this issue Sep 12, 2024 · 0 comments
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that

Comments

@jeremysimmons
Copy link

I'm struggling to find resources & guidance for using the azure sdk in writing a multi-tenant application.

How do we consume the service Client types (BlobClient, ArmClient, etc) and respect the credentials that are unique to each tenant (we use ClientCertificateCredential).

Additionally, how do we do this using dependency injection?

I am possibly just missing it, but I have not found that the scenario of writing multi-tenant applications to be well addressed.

Thanks!

@github-actions github-actions bot added customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Sep 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Projects
None yet
Development

No branches or pull requests

1 participant