Alternative for 'ResponseStreamEventType' from 'azure.ai.projects.models' is not documented

[henryshires]

• Package Name: azure-ai-projects
• Package Version: 2.0.0b4 and above
• Operating System: Windows
• Python Version: 3.13.9

Describe the bug
The ResponseStreamEventType enum is no longer available in azure.ai.projects.models using package version 2.0.0b4 or above. This is used to help capture streaming response events from openai_client.responses.create() without the need for string literals. This change was not documented in CHANGELOG.md or in Foundry code samples despite the GitHub repo samples being updated.

To Reproduce
Steps to reproduce the behavior:

1. Use the sample code from Foundry for workflows OR Attempt to import ResponseStreamEventType from azure.ai.projects.models
2. Run-time error Cannot import name 'ResponseStreamEventType' from 'azure.ai.projects.models'

Expected behavior
The package import to exist or for clear breaking change documentation to migrate to string literals in the CHANGELOG.md

Screenshots
Official Foundry code samples and documentation say beta4 and above is supported.

[kashifkhan]

Thank you for the feedback @henryshires . I've routed this to the right folks, who can help you further

[github-actions]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @bobogogo1990 @dargilco @glharper @howieleung @kingernupur @nick863 @trangevi @trrwilson.

[dargilco]

@henryshires Thank you for reporting this. This is by design, the package azure-ai-projects does not include any classes related to handling openai client calls (.responses, .conversations, .evals). Typically developers use Dicts as input and to parse output, and that's what you see in all OpenAI Python samples.

[henryshires]

@dargilco no problem, and yes thank you for that clarification. I understand the design choice here, I am looking for breaking changes like these to be more documented clearly in the future. It got lost/didn't make the breaking changes list and is still being recommended by Microsoft's first-party documentation/Foundry samples.

[dargilco]

Thank you for the feedback!

Now that we have transitioned to stable releases, there won't be any more breaking changes, other perhaps on features that are still in preview (like the ".beta" operations). We are doing a better job keeping the public docs updated immediately when we do a release, but if you still see code sample on Foundry UI or learn.microsoft that is stale, please open a GitHub issue here and tag me.

[henryshires]

Will do! Thanks for the quick response.