-
Notifications
You must be signed in to change notification settings - Fork 67
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
Add document for deploying managed identity #39
Conversation
README.md
Outdated
@@ -24,7 +24,10 @@ This open source project is fully backed by the Microsoft Healthcare team, but w | |||
- A FHIR mapping template uploaded to the template storage container. See [Configuration](./docs/Configuration.md) for more information. | |||
|
|||
# Getting Started | |||
To get started you can deploy the [IoMT FHIR Connector for Azure](./docs/ARMInstallation.md) by itself or start with a complete [sandbox environment](./docs/Sandbox.md) that includes an instance of [IoT Central](https://azure.microsoft.com/en-us/services/iot-central/) with simulated devices and a deployed instance of the [Azure API for FHIR](https://docs.microsoft.com/en-us/azure/healthcare-apis/). | |||
To get started, there are a few options: | |||
1. Deploy the [IoMT FHIR Connector for Azure](./docs/ARMInstallationManagedIdentity.md) by itself for use with Azure API for FHIR and Azure Active directory in the same subscription |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does it mean managed identity flavor of IoMT connector doesn't work if Azure API for FHIR and IoMT Connector are on different subscriptions? If yes, we may want to cover this use case in #2 line item.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe so, but @namalu or @dustinburson can confirm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it is more correct to say it won't work if they are on different tenants but in principle yes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added a few comments.
Looks great overall, thanks for putting this together on a short notice.
Adding documentation for installing the connector using managed identity to connect to Azure API for FHIR, including the "easy button"