![]() ![]() This scope is typically used for enabling actionable messages from a service that is specific to your organization, like a line- of-business application internal to your organization. Organization: This enables actionable message from your service to any Microsoft 365 email user within your organization.This scope is generally used for testing actionable messages integration with few test users that you have specified. Test Users: This enables actionable emails from your service to some of the O365 email users in your organization. ![]() In this section, you need to specify at what scope you want to enable actionable message for your service. įor an example of how to get public key XML from a. The format for this field is an RSAKeyValue element. Public Key: If you plan to send actionable messages as Signed Card, then you need to specify the public key corresponding to the private key you will use for signing the card. Your target URL can correspond to the top level domain or the sub-domain of the TLD. Example: URLs: This is one or more domains corresponding to URLs that will process the actions. Sender email address: This is one or more static email addresses corresponding to the service that will send out emails with action markup. In this section, you need to supply key details that will allow Office 365 to accept emails with markup from your service as well as URLs that can be invoked via the action buttons from those emails. The developer dashboard is divided into a few logical sections you need to fill out based on the scope you'd like to request Microsoft to enable actionable message from your service.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2023
Categories |