I have recently configured a webhook for Microsoft Graph for the following:
security/alerts?$filter=status eq 'newAlert'
How can I simulate a test alert to see if it works or is there a method that I can use to achieve this?
There's really no way to generate a test alert, unfortunately. You would have to pay for a subscription to at least of the alert providers like ASC, MCAS, AIP, MDATP, Sentinel, etc. You may be able to try a trial subscription if one is offered.
Related
A few weeks ago I implemented my first REST integration with the DocuSign API. Things over all went smoothly and with very little complaints. One particular hang up I experienced though was some confusion in regards to the Developer account and how it relates to the General account. I started with a developer account and used the test credentials to build my integration. Once my integration passed inspection it required me to choose another paid docusign account that the integration key would "go live" on. This is all pretty straight forward.
The curve ball came when I actually went to purchase the API account and it said, "you aren't eligible to purchase this". There isn't clear instruction on the site, so my questions are:
1.) In what order does the account creation need to go? Developer > General (Paid) > API Plan (Paid)?
2.) Does DocuSign expect the user, as the customer, to purchase the plan or should that plan be purchased through my developer account?
I tried to reach out to customer service directly, but it was pretty much a, "give us all of your money, then we'll help" situation. I have several customers who are interested in this integration, but I'm not comfortable presenting this as an option until I get a better understanding of the process. Any advice is greatly appreciated.
In general, DocuSign does require a paid account to complete the Go Live process. If you - the integration owner - will not be using DocuSign yourself, you would want to reach out to the [DocuSign Partners program][1] to receive a free Partner account that can hold your integration key instead of having to purchase one.
From there, the end users of your integration can purchase their own DocuSign accounts. You could potentially act as a reseller of DocuSign if you were so inclined.
https://www.docusign.com/partners/become-partner
If you still need assistance, please email apihelp#docusign.com with this information. Someone will help you right away.
Testing out the platform I was running on both a developer account and a Trial Business Pro account until I purchased a standard plan.
Up until I purchased the standard plan, envelope statuses would update by the second and the functionality built with the Apex Toolkit was working well.
Once changing to the standard paid plan, envelopes statuses take 10-15 minutes to update and some functionality is not working.
My question is:
Do the different plans have different status updating times in Salesforce?
Is functionality of the Apex Toolkit limited between the different plans?
Does the Connect option (which is missing now) have anything to do with the above?
Thanks!
They do not. Writeback to Salesforce takes place via DocuSign Connect. Some plans don't support Connect out of the box but the actual writeback times / delays do not differ between account plan types.
Indirectly, the only way that a plan type can interfere with an API call that worked on another plan type is if it had entitlement to a feature that your new plan does not, IE: The ability to allow Comments, to set recipient signing language, to set envelopeID Stamp Control, etc...
I would highly suspect that it does -- in fact I'm a little surprised that your writebacks are happening at all if you don't have Connect enabled. Salesforce adds an object reference IE: Opportunity / AccountIds to the envelope's custom fields on send. When Connect sees these fields, it knows to write back to that specific object. Without Connect enabled and configured it shouldn't be able to process these writebacks at all.
I think you should have a conversation with your Account Rep first regarding Connect entitlement, then you can reconnect your Salesforce instances to the updated DocuSign account which is something that we can help you with.
Regards,
Matt
I am trying to call the Azure billing rate card api. The call is happening successfully after the authentication because the status code is OK. But though I have a vm in the corresponding resource group and subscription, always getting response as:
{"value":[]}
Same is happening in case of azure billing usage api. I had seen one question asked for billing usage api but I have tried all the options mentioned like keep the duration for 3 months, don’t keep future date etc, yet there is no response”:
{"value":[],
nextLink:”https://….”}
Please let me know the issue could be abd because of which both rate card and usage api are not returning right data.
Thanks
You were right, I had the same problem and i resolved it on giving 'reader' persmission on my servie account in my subscription .
Thx a lot !
I been working on a app where the common user can subscribe to different plans, which give different perks.
I been trying to do this by using Stripe's payment component from xamarin component store
But for me, it seems like this component only give you the option to request a payment, but not subscript to a plan.
this leave me think, the only way i can make this happen, is to make the whole "payment and subscriptions to the plan" code on native IOS and Android, which i after bind up against my PCL
So to conclude what i'm looking for is a more simple way to create this functionality,
Thanks for your time,
So the Xamarin extension should really only be used to collect the credit card details and "tokenize" the card. The actual handling of the charge is done by your backend server (as described in the documentation for the extension under "Sending the token to your server"). Once you pass the otken to your backend, you can actually do anything you like with it-- including attach it to a Customer Record by setting the source-attribute when calling the Create a Customer API Endpoint. Once you've created the Customer record, you can then create a Subscription using your Plans.
I was trying to query the usage and billing API that Azure recently recently and saw that I can use the following API to get the rate card:
https://management.azure.com/subscriptions/{subscription-id}/providers/Microsoft.Commerce/RateCard?api-version=2015-06-01-preview&$filter=OfferDurableId eq '{offer-id}' and Currency eq 'USD' and Locale eq 'en-US' and RegionInfo eq 'US'
However, this requires I need to explicity know the offerDurableId, which I came to know for my case from Azure's website.
Is there an API that will give me these offer codes?
AFAIK, there is no API to get the offer codes. In fact if you look at Billing API documentation here, they also ask you to get the information about this from the link you mentioned.
Set {OfferDurableId} to a valid Offer ID code (e.g., MS-AZR-0026P).
See Microsoft Azure Offer Details for more information on the list of
available Offer IDs, country/region availability, and billing
currency. The Offer ID parameter consists of the “MS-AZR-“ prefix,
plus the Offer ID number.
Considering the offer code don't change, I think it is somewhat safe to save this information in your own database
One possibility is this. But it's not documented or supported officially. It's the API which the Azure Portal calls to get the offer information.
https://stackoverflow.com/a/54324041/9893001
There is not public API for this, but there is a feature request, please vote for it.