You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -180,7 +180,7 @@ This template uses Azure Key Vault to store all connections to communicate betwe
180
180
181
181
This template also uses [Managed Identity](https://learn.microsoft.com/entra/identity/managed-identities-azure-resources/overview) for local development and deployment.
182
182
183
-
To ensure continued best practices in your own repository, we recommend that anyone creating solutions based on our templates ensure that the [Github secret scanning](https://docs.github.com/code-security/secret-scanning/about-secret-scanning) setting is enabled.
183
+
To ensure continued best practices in your own repository, we recommend that anyone creating solutions based on our templates ensure that the [GitHub secret scanning](https://docs.github.com/code-security/secret-scanning/about-secret-scanning) setting is enabled.
184
184
185
185
You may want to consider additional security measures, such as:
Copy file name to clipboardExpand all lines: TRANSPARENCY_FAQS.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,4 +26,4 @@ The system allows users to review, reorder and approve steps generated in a plan
26
26
27
27
## What operational factors and settings allow for effective and responsible use of Multi Agent: Custom Automation Engine – Solution Accelerator?
28
28
Effective and responsible use of the Multi Agent: Custom Automation Engine – Solution Accelerator depends on several operational factors and settings. The system is designed to perform reliably and safely across a range of business tasks that it was evaluated for. Users can customize certain settings, such as the planning language model used by the system, the types of tasks that agents are assigned, and the specific actions that agents can take (e.g., sending emails or scheduling orientation sessions for new employees). However, it's important to note that these choices may impact the system's behavior in real-world scenarios.
29
-
For example, selecting a planning language model that is not well-suited to the complexity of the tasks may result in lower accuracy and performance. Similarly, assigning tasks that are outside the system's intended scope may lead to errors or incomplete results. Users can choose the LLM that is optimized for responsible use. The default LLM is GPT-4o which inherits the existing RAI mechanisms and filters from the LLM provider. Caching is enabled by default to increase reliability and control cost. We encourage developers to review [OpenAI’s Usage policies](https://openai.com/policies/usage-policies/) and [Azure OpenAI’s Code of Conduct](https://learn.microsoft.com/en-us/legal/cognitive-services/openai/code-of-conduct) when using GPT-40. To ensure effective and responsible use of the accelerator, users should carefully consider their choices and use the system within its intended scope.
29
+
For example, selecting a planning language model that is not well-suited to the complexity of the tasks may result in lower accuracy and performance. Similarly, assigning tasks that are outside the system's intended scope may lead to errors or incomplete results. Users can choose the LLM that is optimized for responsible use. The default LLM is GPT-4.1 which inherits the existing RAI mechanisms and filters from the LLM provider. Caching is enabled by default to increase reliability and control cost. We encourage developers to review [OpenAI’s Usage policies](https://openai.com/policies/usage-policies/) and [Azure OpenAI’s Code of Conduct](https://learn.microsoft.com/en-us/legal/cognitive-services/openai/code-of-conduct) when using GPT-4.1. To ensure effective and responsible use of the accelerator, users should carefully consider their choices and use the system within its intended scope.
If you select the Retail Marketing Content Generation team, follow the prompts below.
123
+
124
+
>**Agents Used:** Triage, Planning, Research, Text Content, Image Content, Compliance
125
+
126
+
The Retail Marketing Content Generation Scenario allows users to generate end-to-end marketing assets (copy + image) for retail campaigns, grounded in the Contoso Paint product catalog. Key tasks include:
127
+
128
+
_Sample operation:_
129
+
130
+
- Task: Switch to the **"Retail Marketing Content Generation Team"** from the top left section and click **"Continue"** button.
131
+
- Task: From the Quick Tasks, select **"Generate a social media post"** and submit it.
132
+
133
+
> _Note: Average response time is 30–60 seconds for plan generation._ <br>
134
+
> _Observe: It will trigger the "Generating Plan Action" and give the Proposed Plan with 5 or more Steps (Planning → Research → Text Content → Image Content → Compliance)._
135
+
</br>
136
+
137
+
- Task: Click on **"Approve Task Plan"** Button.
138
+
> _Note: Average response time is around 2–3 minutes (image generation included)._ <br>
139
+
> _Observe: It goes into "Thinking Process", "Processing your plan" and "coordinating with AI Agents". The final output includes marketing copy (headline, body, CTA, hashtags), a rendered campaign image, and a compliance review._ <br>
140
+
> _Review the output._
141
+
120
142
121
143
This structured approach ensures that users receive automated, AI-coordinated task execution and intelligent responses from specialized agents.
Copy file name to clipboardExpand all lines: docs/TroubleShootingSteps.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -166,4 +166,4 @@ Use these as quick reference guides to unblock your deployments.
166
166
---------------------------------
167
167
168
168
💡 Note: If you encounter any other issues, you can refer to the [Common Deployment Errors](https://learn.microsoft.com/en-us/azure/azure-resource-manager/troubleshooting/common-deployment-errors) documentation.
169
-
If the problem persists, you can also raise an bug in our [MACAE Github Issues](https://github.com/microsoft/Multi-Agent-Custom-Automation-Engine-Solution-Accelerator/issues) for further support.
169
+
If the problem persists, you can also raise a bug in our [MACAE GitHub Issues](https://github.com/microsoft/Multi-Agent-Custom-Automation-Engine-Solution-Accelerator/issues) for further support.
You got it! I've initiated a background check and everything looks good to go— You're ready to move onto helping Jessica set up and Office 365 account. Want me to hand that over to your Manager Agent?
48
+
You got it! I've initiated a background check and everything looks good to go— You're ready to move onto helping Jessica set up an Office 365 account. Want me to hand that over to your Manager Agent?
Are you sure you want to delete "{teamToDelete?.name}"?
722
722
</DialogTitle>
723
723
<TextclassName={styles.deleteConfirmText}>
724
-
This team configurations and its agents are shared across all users in the system. Deleting this team will permanently remove it for everyone, and this action cannot be undone.
724
+
This team configuration and its agents are shared across all users in the system. Deleting this team will permanently remove it for everyone, and this action cannot be undone.
0 commit comments