Microsoft 365 Health/Announcements Connector (Independent Publisher)

[techienickb]

---

When submitting a connector, please check the following conditions for your PR to ensure a smooth certification process.

• [x] I attest that the connector works and I verified by deploying and testing all the operations.
• [x] I attest that I have added detailed descriptions for all operations and parameters in the swagger file.
• [x] I validated the swagger file, apiDefinition.swagger.json, by running paconn validate command.
• [x] If this is a certified connector, I confirm that apiProperties.json has a valid brand color and doesn't use an invalid brand color, #007ee5 or #ffffff. If this is an independent publisher connector, I confirm that I am not submitting a connector icon.

If you are an Independent Publisher, you must also attest to the following to ensure a smooth publishing process:

• [x] I have named this PR after the pattern of "Connector Name (Independent Publisher)" ex: HubSpot Marketing (Independent Publisher)
• [x] Within this PR markdown file, I have pasted screenshots that show: 3 unique operations (actions/triggers) working within a Flow. This can be in one flow or part of multiple flows. For each one of those flows, I have pasted in screenshots of the Flow succeeding.
• [x] Within this PR markdown file, I have pasted in a screenshot from the Test operations section within the Custom Connector UI.
• [x] If the connector uses OAuth, I have provided detailed steps on how to create an app in the readme.md.

[ghost]

All CLA requirements met.

[natalie-pienkowska]

Thanks for submitting an Independent Publisher Connector! :) Since this is a connector to a 1st party service, we will be in touch with you shortly.

[techienickb]

@sriyen-msft updated as requested

[techienickb]

Updated to use v1.0 of graph as this has been released and is no longer in beta

[techienickb]

@sriyen-msft will try again, I originally did the descriptions in the GUI and re-exported which is why some lower level object descriptions were missed

[Laskewitz]

@natalie-pienkowska just an FYI... this is a Graph API connector. Should probably go into the standard bucket. You might've already seen this - but just to be sure :)

[techienickb]

@sriyen-msft fixed swagger validation errors, should be good to go, unless MS wants to make it a first party connector (which would be nice)

[sriyen-msft]

[[certify-connector]]

[sriyen-msft]

@techienickb Apologies for the delay in response, We are actively working on preparing and deploying your connector to publish environments. As you know that we are deploying the connector as a Standard connector, For that, we need to go thru a few guidelines and approvals from the concerned teams (ex. Power BI API team) which is a bit lengthy process. Please allow us some more time, we will keep you posted with the updates and deployment plan soon. Thank you so much for your patience.

[Amjed-Ayoub]

Dear partner,

We apologize for the delay you might be experiencing while we are working on a high volume of connector requests. Rest assured that we are doing everything we can to address this volume. We are taking measures like improving our processes and hiring additional team members to guarantee resolving your connector requests in a timely manner.

Please let us know if you have any questions in the meantime.

[Amjed-Ayoub]

Hi @techienickb, I hope you are doing well. Unfortunately, we couldn't get a permission from the Graph API due to an internal reason. We are looking for alternate method of authentication for your connector. We currently don’t have an estimated date in mind for deploying your connector. Rest assured that we are doing our best trying to get authorization for your connector. Apologies for any inconvenience this may cause. Thank you so much for your patience and understanding.

[vmanoharas]

Hello @techienickb, I hope you are doing well. Apologies for the delay in response, as the connector certification team was in transition, we could not take your connector further. If you would like to go as independent publisher with your connector. Could you please close this and resubmit as new connector? so that we can adhere to new process. Since this is on-hold for many days.