{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":21043,"path":"integrate-applications/integration-hub/azure-notif-hub-spoke.md","title":"Microsoft Azure Notification Hub Spoke","bundle":null,"doc_type":null,"release":"australia","body":"\n# Microsoft Azure Notification Hub Spoke\n\nIntegrate ServiceNow instance with Microsoft Azure Notification Hub. Manage Azure notification hubs from your ServiceNow instance.\n\n## Request apps on the Store\n\nVisit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) to view all the available apps, and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the [ServiceNow Store version history release notes](https://www.servicenow.com/docs/r/store-release-notes/sn-store-release-notes.html).\n\n## Integration Hub subscription\n\nThis spoke requires an Integration Hub subscription. For more information, see [Legal schedules - IntegrationHub overview](https://www.servicenow.com/content/dam/servicenow-assets/public/en-us/doc-type/legal/snc-addendum-integrationhub.pdf).\n\n## Spoke version\n\nMicrosoft Azure Notification Hub spoke v2.0.0 is the latest version. For version history of the spoke, see [Microsoft Azure Notification Hub spoke release notes](https://www.servicenow.com/docs/r/store-release-notes/store-integrationhub-rn-microsoft-azure-notification-hub.html).\n\n## Supported versions\n\nThis spoke was built for Azure Notification Hub version 2023-09-01, but may be compatible with later versions.\n\n## Spoke requirements\n\n- Storage account in your Microsoft Azure portal for integration with your ServiceNow instance.\n- Register the application in the Microsoft Azure portal and record the access keys and directory IDs.\n\n## Spoke dependencies\n\nIf you’re having trouble installing the app, verify that these dependent plugins are installed:\n\n- ServiceNow IntegrationHub Action Step - REST \\(com.glide.hub.action\\_step.rest\\)\n- ServiceNow Flow Designer - Dynamic Inputs \\(com.glide.hub.dynamic\\_inputs\\)\n- Flow Designer Action Step - Payload Builder \\(com.glide.hub.action\\_step.payload\\)\n- ServiceNow IntegrationHub Runtime \\(com.glide.hub.integration.runtime\\)\n- Complex Object \\(com.glide.cobject\\)\n- Get Connection Info \\(com.glide.hub.action\\_step.get\\_connection\\_info\\)\n- ServiceNow IntegrationHub Action Template - Data Stream \\(com.glide.hub.action\\_type.datastream\\)\n- IHUB Spoke Util Pack \\(com.snc.ihub\\_spoke\\_util\\_pack\\)\n- Microsoft Azure Resource Management Spoke is installed and the connection record configured on your ServiceNow instance.\n- Microsoft Azure Notification Hub SAS connection and credential alias record is configured on your ServiceNow instance.\n\n**Note:** Some of these plugins are licensable features and require appropriate licenses, if used outside the spoke implementation.\n\n## Spoke actions\n\nThe Microsoft Azure Notification Hub Spoke provides actions to automate Azure Notification Hub tasks when events occur in your ServiceNow instance. Available actions include:\n\n\n
\n\nCategory\n\n\n\nAction\n\n\n\nDescription\n\n
\n\nInstallation Management\n\n\n\nCreate or Update Installation\n\n\n\nCreates or updates an installation.\n\n
\n\nDelete Installation\n\n\n\nDeletes an installation.\n\n
\n\nLook up Installation\n\n\n\nRetrieves installation based on the Installation ID.\n\n
\n\nUpdate Installation\n\n\n\nPartially updates an installation using the JSON-Patch.\n\n
\n\nLook up Namespaces Stream by Resource Group\n\n\n\nReturns the list of available namespaces within a resource group.\n\n
\n\nLook up Namespaces Stream by Subscription ID\n\n\n\nReturns the list of available namespaces within the subscription.\n\n
\n\nNamespace Management\n\n\n\nLook up Namespace\n\n\n\nReturns the details of the specified namespace.\n\n
\n\nCreate or Update Namespace\n\n\n\nCreates or updates a Notification Hub namespace. **Note:** This operation is idempotent.\n\n
\n\nDelete Namespace\n\n\n\nDeletes an existing namespace. This operation also removes all associated Notification Hubs under the namespace.\n\n
\n\nUpdate Namespace\n\n\n\nPatches the existing namespace.\n\n
\n\nNotification Hub Management\n\n\n\nCreate or Update Notification Hub\n\n\n\nCreates or updates a Notification Hub in a namespace.\n\n
\n\nDelete Notification Hub\n\n\n\nDeletes a notification hub associated with a namespace.\n\n
\n\nLook up Notification Hub\n\n\n\nReturns the details of the specified notification hub.\n\n
\n\nLook up Notification Hubs Stream by Namespace\n\n\n\nReturns the list of available notification hubs associated with a namespace.\n\n
\n\nRegistration Management\n\n\n\nCreate APNS Registration\n\n\n\nCreates a registration for an Apple Push Notification service \\(APNS\\) device. This method generates a registration ID that you can use to retrieve, update, and delete this registration.\n\n
\n\nCreate GCM Registration\n\n\n\nCreates a registration for Google Cloud Messaging \\(GCM\\) device. This method generates a registration ID that you can use to retrieve, update, and delete this registration.\n\n
\n\nCreate Registration ID\n\n\n\nReturns a registration ID \\(without creating a registration\\).\n\n
\n\nDelete Registration\n\n\n\nDeletes a registration.\n\n
\n\nLook up Registration\n\n\n\nRetrieves information about a registration.\n\n
\n\nUpdate APNS Registration\n\n\n\nUpdates an existing APNS registration.\n\n
\n\nUpdate GCM Registration\n\n\n\nUpdates an existing GCM registration.\n\n
\n\nLook up Registrations Stream\n\n\n\nRetrieves all registrations.\n\n
\n\nNotification Management\n\n\n\nSend APNS Native Notification\n\n\n\nSends an APNS native notification through a Notification Hub.\n\n
\n\nSend GCM Native Notification\n\n\n\nSends a GCM native notification through a Notification Hub.\n\n
\n\nSend Notification to Device Handle\n\n\n\nSends a notification directly to a device handle \\(a valid token as expressed by the Notification type\\). **Note:** Users of this API don’t need to use Registrations or Installations.\n\n
## Connection and credential alias requirements\n\nIntegration Hub uses aliases to manage connection and credential information, and OAuth credentials. Using an alias eliminates the need to configure multiple credentials and connection information profiles when using multiple environments. If the connection or credential information changes, you don't need to update any actions that use the connection.\n\nFor information about setting up the spoke, see [Set up the Microsoft Azure Notification Hub spoke](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/integration-hub/setup-azure-notif-hub.md).\n\n"}}