Adding Bicep provisioning scripts and other configuration utility scripts#265
Merged
rodrigobr-msft merged 2 commits intomainfrom Aug 27, 2025
Merged
Conversation
tracyboehrer
approved these changes
Aug 26, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request introduces a comprehensive set of scripts, Bicep templates, and documentation to automate the provisioning and configuration of Azure Bot Service resources, Microsoft Teams manifests, and associated Azure AD App Registrations for several SDK samples. The changes enable streamlined deployment for scenarios such as Teams SSO, Auto Sign-In, and OBO Authorization.
Infrastructure provisioning and configuration scripts:
bot.bicep), App Registrations with OAuth configuration (oauth_app.bicep), and simple App Registrations (simple_app.bicep), as well as connection resources for OAuth providers (oauth.bicep). These templates leverage the Microsoft Graph Bicep extension for advanced resource management. [1] [2] [3] [4] [5]provision.ps1,prov_app.ps1, andprov_bot.ps1for automated deployment, anddecompose.ps1for inspecting existing resource configurations. [1] [2] [3] [4]Teams manifest generation and configuration:
gen_teams_manifest.ps1) to generate a Microsoft Teams manifest JSON file based on a provided App ID, simplifying the process of packaging and importing the bot into Teams.manifest.json) in thebotdirectory, demonstrating required structure and configuration for Teams SSO bots.Documentation and sample structure:
auto-signin,obo-authorization, and general samples), explaining deployment steps, resource relationships, and manual configuration requirements. [1] [2] [3] [4]Bicep configuration and extension usage:
bicepconfig.json) to enable extensibility features and specify the Microsoft Graph extension for advanced resource management.These changes collectively provide a robust foundation for automating the deployment and configuration of Teams-integrated bots and their supporting Azure resources, improving developer productivity and reproducibility for the SDK samples.