office365Outlook connector - meeting invitation not being sent to required attendees

[Madumi]

I'm wondering if there's something I've done wrong in my code. Calendar events post successfully on my calendar ("Calendar Name"), but required attendees do not receive a notification email (they receive one on an event removal, but not when it is created).

Required attendees are individuals outside of the current environment, but I wouldn't think that would stop the email going out (?).

here's the code:

Office365Outlook.V4CalendarPostItem(
    LookUp(
        Office365Outlook.CalendarGetTables().value,
        DisplayName = "Calendar Name",
        Name
    ),
    Concatenate("Audit - ",Text(galProjects.Selected.'Project Name')),
    galProjects.Selected.'Received Date',
    galProjects.Selected.'Received Date',
    "(UTC-06:00) Central Time (US & Canada)",
    {
        requiredAttendees: "email@outsidetenant.com;email@gmail.com",
        body: Text(galProjects.Selected.Notes),
        importance: "high",
        responseRequested: true
    }
)

Any suggestions would be great! thx!

[GarethPrisk]

Is your required attendees parameter set with real data in your app? As written, that's not going anywhere. 🙃

[Madumi]

@GarethPrisk  Thanks so much for your reply.

Do you mean are the email addresses real addresses? I put

"email@outsidetenant.com;email@gmail.com"

in just as filler text, in the app, those emails are correct addresses.

Does that clarify?

[GarethPrisk]

That does, thanks!

I ended up using your code and making it very simple. It worked...

Office365Outlook.V4CalendarPostItem(
    LookUp(
        Office365Outlook.CalendarGetTables().value,
        DisplayName = "Calendar", // Double check this value, by hovering the request above
        Name
    ),
    "Test Appointment Subject",
    Now(),
    Now(),
    "(UTC-06:00) Central Time (US & Canada)",
    {
        requiredAttendees: "mypersonalemail@gmail.com", // This worked as a single recipient, and I received the email (from work domain to personal gmail)
        body: "Test Appointment Body",
        importance: "high",
        responseRequested: true
    }
)

Basically, with simple and supported inputs, the Connector and that function appear to work as intended.

• From my work domain
• Appointment showed up in Outlook almost immediately
• Email to non-work domain showed up almost immediately, as Appointment to accept

Might be worthwhile to explore:

• Ensure there's nothing invalid with any of the control's value's you're passing - you seem sharp, so this is doubtful
• Setup a simple test example, like above, and see if it works in the simplest scenario
  • Single recipient, internal
  • Single recipient, external
  • Multiple, internal
  • Etc.
• Maybe see if your organization has any policies and/or Exchange transport rules, which may be impacting the sending of emails for appointments

[v-siky-msft]

@Madumi 

I have made a test based on your formula, but I don't have any issue you mentioned. The users can get the event invitation properly.

As an alternative workaround, could you please add an 'Office365Outlook.SendEmailV2()' function after the codes to send a separate email reminder to attend the event.

Sik

[Madumi]

@v-siky-msft& @GarethPrisk 

Thanks so much for replies. I think I am getting closer to finding the problem, but wondered if anyone could direct me.

If I change the connector action from V4CalendarPostItem, to V3CalendarPostItem, it works... However, this breaks other functions (eg. in other code, I cannot reliably call the Calendar names from what V3CalendarPostItem posted using CalendarGetTablesV2).

Why would V4 fail when V3 works? i.e. V4 fails to send the notification email to accept the event, whereas V3 sends it correctly.

[Madumi · Accepted solution]

Aaaah, finally, I received the NDR messages for failed delivery:

5.7.708 Access denied, traffic not accepted from this IP

I'll contact support to have the block removed...

----------------Edited to add: As it turns out, the office 365 account from which I was attempting to send email, did not (yet) have the full DNS MX records for sending mail (I attempted to use spf records alone to authorize the outlook server). Once those MX/spf/CNAME records were all in place, mail could be sent correctly using the Office365Outlook connector. - my bad!

[v-siky-msft]

@Madumi 

Thanks for sharing the workaround, I learned from that.

Could you please mark your workaround as the answer if your issue is fixed after the block is removed.

Sik