title: Microsoft graph gives an error of 403 Forbidden when subscribing to notifications API for the 12th group subscription
body: <p>I am using an Azure function for subscribing to Microsoft Graph notifications API for group updates. I need to subscribe to around 100 groups belonging to the same tenant, using one common notificationUrl. </p>
  
  <p>According to online documentations <a href="https://docs.microsoft.com/en-us/graph/webhooks#notifications" rel="nofollow noreferrer">here</a>, we have the limitations as below.</p>
  
  <p><strong>Certain limits apply to Azure AD based resources (users, groups) and may generate errors when exceeded:</strong></p>
  
  <p><strong>Per app: 50,000 total subscriptions</strong></p>
  
  <p><strong>Per tenant: 35 total subscriptions across all apps</strong></p>
  
  <p><strong>Per app and tenant combination: 7 total subscriptions</strong></p>
  
  <p><strong>Azure AD B2C tenants are not supported.</strong></p>
  
  <p><strong>Notification for user entities are not supported for personal Microsoft accounts.</strong></p>
  
  <p>I have created a function and was able to create 11 active subscriptions and receive notifications:</p>
  
  <p>•   1 subscription to all groups on a tenant, created 2 days back.</p>
  
  <p>•   10 subscriptions which are to specific groups and on the same tenant, today.</p>
  
  <p>On trying to create the 12th subscription to another group in the same tenant, i am getting a 403 Forbidden response from Graph when sending create subscription request. I have deleted some active subscriptions and tried to create, and it again fails to create the 12th active subscription.</p>
  
  <p>Any suggestion/answers to the following would be of great help:</p>
  
  <ol>
  <li>The numbers mentioned in above limitations are not matching to our scenario where we can have only 11 active subscriptions. Is there any additional scenario/case that exists which is stopping from creating further subscriptions to same notificationUrl?</li>
  <li>Since i tried to create 10 subscriptions continuously within an hour’s time, is there any rule as to only a limited number of subscriptions can be created in a specific interval of time to the same notificationUrl? 
  And if this case is true, we were able to delete and create exactly same number of active subscriptions. </li>
  <li>Bit of explanation of the above limitations would be useful so that the impact of these limitations is more clear to me in this scenario.</li>
  </ol>