Update deploy_features.md

[YIN-Renlong]

Purpose

Added detailed instructions for setting up GPT-4 and GPT-4o deployments. Included specific commands for deployment names, model versions, and deployment capacities. Clarified steps for setting deployment capacity with a note on default values for GPT-4o.

Does this introduce a breaking change?

When developers merge from main and run the server, azd up, or azd deploy, will this produce an error?
If you're not sure, try it out on an old environment.

[ ] Yes
[x] No

Does this require changes to learn.microsoft.com docs?

This repository is referenced by this tutorial
which includes deployment, settings and usage instructions. If text or screenshot need to change in the tutorial,
check the box below and notify the tutorial author. A Microsoft employee can do this for you if you're an external contributor.

[ ] Yes
[x] No

Type of change

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[x] Documentation content changes
[ ] Other... Please describe:

Code quality checklist

See CONTRIBUTING.md for more details.

• The current tests all pass (python -m pytest).
• I added tests that prove my fix is effective or that my feature works
• I ran python -m pytest --cov to verify 100% coverage of added lines
• I ran python -m mypy to check for type errors
• I either used the pre-commit hooks or ran ruff and black manually on my code.

[YIN-Renlong]

@microsoft-github-policy-service agree

[pamelafox]

Thanks so much! Would love if you could add -mini instructions while you're in this file.

[YIN-Renlong]

Thanks so much! Would love if you could add -mini instructions while you're in this file.

Hi @pamelafox, thanks. I have made the suggested changes, including adding instructions for the -mini model. Please review the updated file. Thanks!

[pamelafox]

The markdownlint checker isn't happy. The markdown extension will auto-fix it locally, I can do it locally once I'm done testing another branch, or you can do it yourself. (My attempts to fix via GitHub suggestions were not fruitful)

[YIN-Renlong]

The markdownlint checker isn't happy. The markdown extension will auto-fix it locally, I can do it locally once I'm done testing another branch, or you can do it yourself. (My attempts to fix via GitHub suggestions were not fruitful)

Hi @pamelafox, thanks for the heads-up! I've fixed the markdown format according to the markdownlint checker requirements. (I accidentally closed the pull request but have now reopened it.)

[YIN-Renlong]

[pamelafox]

Thank you!