Hello @oizovski,
You’re absolutely right to notice and ask about the expiration date when creating the Application Client Secret in Azure. To address your question directly: Yes, the client secret does need to be renewed periodically.
The expiry time limit you set in Azure while creating the client secret is a security measure. Once this period passes, the secret will become invalid. This means that after the expiry date, the token or credentials FluentSMTP uses to connect to your Microsoft Azure email provider will no longer be valid. Consequently, FluentSMTP will stop being able to send emails through that connection.
To ensure your email sending remains uninterrupted, you will need to reconfigure the connection again by generating a new client secret within your Microsoft Azure application. After you’ve created the new secret in Azure, you’ll simply need to update your existing Microsoft connection settings in FluentSMTP with this new secret. You won’t typically need to set up the entire connection from scratch, just update that specific credential field and regenerate the token.
I highly recommend setting a reminder for yourself a little before the expiration date or set a longer expiry date. This way, you can generate a new secret and update it in FluentSMTP proactively, avoiding any potential disruption in your email delivery.
I hope this explanation helps clarify things for you!
I understand, thank you very much for the information.
