BeyondTrust PM Cloud - Updated connector template to utilize a pre-built ZIP for more seamless deployment#13581
Conversation
…e verbiage on connector landing page
…ctor - Add conditional deployment script for FC1 to upload function package to blob storage - Upload package as 'released-package.zip' with kudu-state.json metadata (matches Azure Functions deployment pattern) - Configure functionAppConfig for FC1 with blob container deployment storage - Add managed identity and Storage Blob Data Contributor RBAC for deployment script - Conditional logic ensures zero impact on Y1/EP1/EP2/EP3 hosting plans (still use WEBSITE_RUN_FROM_PACKAGE) - FC1 uses BeyondTrust__ prefix for app settings, Y1/EP uses BeyondTrust: prefix - Tested and verified: Functions load correctly, data flows to Log Analytics
- Clarify that customers can create OAuth API credentials directly in their PM Cloud instance - Remove reference to contacting BeyondTrust support for API credentials - Improve self-service documentation for data connector setup
- Update remaining references to API credential creation process - Ensure consistent messaging about self-service credential creation
|
Hi @jamos-bt, since you’ve already updated the main template, please update the ZIP package file as well. Thanks! |
|
@v-shukore - Sorry about that. Forgot to repackage that. All done now, and I also synced with the upstream repo while I was at it. |
|
Hi @jamos-bt, |
|
Hi @v-shukore ... here are a few screenshots from the workbook that queries the data ingested into Sentinel by the data connector: 
With regard to the release notes, there is nothing to update. This is still the initial release. We simply changed the deployment method for the Azure Function App code to be more user-friendly as soon as we noticed that during the marketplace listing approval process. Nothing has been published yet though. :) |
|
Hi @jamos-bt, |
|
@v-shukore I've renamed the zip and updated the reference to it in the ARM template. However, I'm not sure what else would need to change. I see other files in the directory for the connector you referenced, but I don't understand what those files are or whether each of them are required. I modeled my own after another solution which utilizes an Azure Function App but that is .NET based just like my own. This one: https://github.com/Azure/Azure-Sentinel/tree/master/Solutions/VaronisSaaS/Data%20Connectors As you can see, my structure and content matches what is present for that connector. In fact, that connector uses a . in the ZIP file name which is why I thought that was acceptable. If there are other changes I need to make, can you please point me to documentation which clearly states what is required? There's so much variation in the content and structure of these various solutions that there's really no way (without official documentation / guidelines) to know what are the actual requirements. |
|
@v-shukore Are we good now that the zip is renamed and we match the structure of other existing .NET Azure Function App connectors? Or are there other specific changes you're requesting? If there are other changes, please see my previous comment and provide a link to documentation that clearly describes the requirements so we can ensure meet them. Thanks! |
|
Hi @jamos-bt, as you confirmed this is .net based connector then its fine. We can move forward with this. Thanks |
4 participants
Change(s):
Reason for Change(s):
Version Updated:
Testing Completed:
Checked that the validations are passing and have addressed any issues that are present: