Skip to content

Conversation

@likebupt
Copy link
Contributor

No description provided.

Copy link
Collaborator

@AliciaFrame AliciaFrame left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Update the readme text so it's not just the text from the word document for the private preview with the CELA boilerplate -- that information needs to be communicated to customers, but doesn't belong in this repo. Phrase it so it's obvious that customers need to request access (see comments in the readme).

Please move the two demos for this private preview - tool calling (https://github.com/microsoft-foundry/fine-tuning/tree/main/Demos/RFT_ToolCall) and Endpoint graders (https://github.com/microsoft-foundry/fine-tuning/tree/main/Demos/EndpointGrader) into the same directory.

Do not move Omkar's Zava Retail Agent into this directory - it's an end to end example from Ignite, and includes other scenarios (e.g. SFT) and should be discoverable on its own. You can link to it from this directory's readme as an example if you want.

- You are being invited to participate in an early private preview for Agentic reinforcement fine tuning with o4-mini/ gpt 5 in Microsoft Foundry/ Azure Open AI service.
- This preview is provided without a service-level agreement, and we don't recommend it for production workloads. Certain features might not be supported or might have constrained capabilities. For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).

## Private Preview Expectations & Limitations:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would remove this section -- these expectations should be communicated to customers participating in the preview, but aren't relevant to the repo itself.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would remove this section -- these expectations should be communicated to customers participating in the preview, but aren't relevant to the repo itself.

I would still keep this, as for all the preview documentation, we have such note at the beginning to avoid potential argument.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants