I have successfully developed the automation, which includes an email-sending functionality. However, I encountered a challenge in the development environment:
Outlook is not installed on the machine.
SMTP cannot be used due to restrictions.
To address this, I explored alternative solutions and found that we can use Office 365 activities in UiPath to send emails directly. This approach enables seamless email communication without requiring Outlook installation. how to proceed on this please provide detailed steps
From the Activities panel, search for Office365 Scope.
Drag and drop this activity into your workflow.
Authenticate the Office 365 Scope:
Inside the Office365 Scope, you’ll need to provide authentication details for your Office 365 account.
For this, UiPath uses OAuth 2.0 authentication via Microsoft Graph API to access services like email.Steps to Authenticate:
Client ID and Tenant ID: Go to the Azure Portal and create a new Azure AD application (if you don’t already have one) to get these credentials.How to Create an Azure AD Application:
In the Azure portal, navigate to Azure Active Directory > App registrations > New registration.
Register your application and note down the Application (client) ID and Directory (tenant) ID.
In Certificates & Secrets, generate a new Client Secret.
Authenticate via the UiPath Office365 Scope Activity:
For the Client ID, use the Application (client) ID you got from Azure AD.
For the Tenant ID, use the Directory (tenant) ID.
Enter the Client Secret you generated in Azure.
You will also need to grant the appropriate permissions for sending emails. This typically involves giving the app Mail.Send permission under API permissions in the Azure portal.
Step 3: Send an Email Using Office 365
Once you have authenticated the Office 365 Scope, you can now send emails using UiPath’s Send Email activity.
Use the Send Email Activity:
Inside the Office365 Scope, search for the Send Outlook Mail Message activity.
Drag and drop this activity under the Office365 Scope.
I am currently working on the development environment (Dev machine) and need to generate the Client ID, Tenant ID, and Client Secret for the bot. I understand that when the bot moves to Production, new credentials will need to be created.
Could you please confirm which email or service account should be used for generating these credentials in both Dev and Prod environments? Additionally, is there any existing process or documentation for managing these credentials during the transition?
Please read through info mentioned in below thread, you will need to have application created for same with required graph api permissions to be able to generate secret and password.
Also you will need to identify which connection method would work for you out of the 4 mentioned in below post.