Ading Azure Open AI to list of models

[aritraghosh]

Added Azure Open AI to the list of models.

Summary by CodeRabbit

• Documentation
  • Updated the README to include Azure OpenAI as a supported LLM provider, with a logo and link to setup documentation.

[coderabbitai]

Walkthrough

The README.md file was updated to add Azure Open AI as a supported LLM provider in the relevant documentation table, including its logo, a label, and a link to the API key setup instructions. No other files or sections were changed.

Changes

File(s)	Change Summary
README.md	Added Azure Open AI as a supported LLM provider with logo, label, and documentation link.

Possibly related PRs

• Update readme #439: Updates the README.md to enhance the "Supported LLM Providers" section by adding new entries and documentation links.
• Readme tools updated with integration logos #451: Updates the README.md by adding new entries with logos and links to improve documentation, focusing on integrations.

Suggested reviewers

• aantn

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ba2fb14 and 6fbc339.

📒 Files selected for processing (1)

• README.md (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• README.md

⏰ Context from checks skipped due to timeout of 90000ms (3)

• GitHub Check: build (3.10)
• GitHub Check: build (3.12)
• GitHub Check: build (3.11)

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

README.md (1)

203-205: Consistent branding for "Azure OpenAI"
The label <strong>Azure Open AI</strong> includes an extra space. Update to use the official "Azure OpenAI" naming for consistency across documentation.

Apply this diff:

-        <strong>Azure Open AI</strong>
+        <strong>Azure OpenAI</strong>

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c76f73d and ba2fb14.

⛔ Files ignored due to path filters (2)

• images/integration_logos/azure-openai.png is excluded by !**/*.png
• images/integration_logos/azure.png is excluded by !**/*.png

📒 Files selected for processing (1)

• README.md (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (3)

• GitHub Check: build (3.12)
• GitHub Check: build (3.10)
• GitHub Check: build (3.11)

🔇 Additional comments (2)

README.md (2)

201-206: Add Azure OpenAI provider entry
The new table cell for Azure OpenAI is correctly inserted between AWS Bedrock and Google Vertex AI, matching the existing structure and styling.

---

201-206:

Details

✅ Verification successful

Verify docs anchor and logo file exist
Ensure that the logo file images/integration_logos/azure-openai.png is present in the repository and that docs/api-keys.md defines a matching section header (e.g. ## Azure OpenAI or ## Azure Open AI) so the generated anchor #azure-openai resolves correctly.

---

🏁 Script executed:

#!/bin/bash
# Verify logo file exists
if [ ! -f images/integration_logos/azure-openai.png ]; then
  echo "ERROR: Missing file images/integration_logos/azure-openai.png"
fi

# Verify API key docs anchor
grep -R -n '^## .*Azure OpenAI' docs/api-keys.md || \
echo "ERROR: No matching header (## Azure OpenAI) found in docs/api-keys.md"

Length of output: 128

---

✅ Verification successful: logo and docs anchor are present
The file images/integration_logos/azure-openai.png exists, and docs/api-keys.md contains the header ## Azure OpenAI (anchor #azure-openai) on line 45. No further changes needed.