I was developing a windows store app integrate with Office 365 API client libraries, But I can't find a interface in office365 api can be used to create a new tenant? Is there any method that can create tenant programmatically.
The Office 365 APIs do not allow you to provision new tenants at this time. If you'd like to see this feature please let the team know at the Office/SharePoint developer UserVoice.
Related
Within Banno Digital Toolkit Admin API, the reports api seems to only support the retrieval of reports that have been already created. Is there a way to create a report through the Admin API in the same way one can create a report in the Banno.com dashboard (Reports->Create request)? It seems the admin API can only call reports already created and not make new ones on its own. Any clarification on this would be helpful. Thanks
[banno-digital-toolkit]
Currently I have been leveraging the documentation here https://jackhenry.dev/open-api-docs/admin-api/api-reference/v0/reports/exports/
I have been unable to find documentation of and api call that can create reports.
Correct, the Admin API does not offer a way to create a report.
We'll take this feedback to the Product & Engineering teams.
We have an API management instance in azure.We have also enabled the management API. There we have set a SAS token & that has been used in the application. Here, we have to change the SAS token in every 30 days. If the token is expired, that will result into an application outage. Is there any way to get notified via email or any other means about the token expiry (in advance). I did some research on this, but , unfortunately could not find anything useful.
I don't believe there is built-in support for this.
You could instead have a logic app that takes in a SAS Token as input and schedules emails based on the expiry of the token.
TIP Apart from an email, you could do more interesting workflows like sending actionable messages using office 365 outlook or https://learn.microsoft.com/en-us/connectors/teams/#post-an-adaptive-card-to-a-teams-channel-and-wait-for-a-response connectors and even create a work item in Azure Devops or create an issue on GitHub, depending on what you use.
Alternatively you could create Azure AD application with client id and client secret, give it permissions to do what you need to be done in APIM and use its credentials to do all the same operations via ARM.
I have an enpoint in my MERN app which I would like to expose to developers.
I came across APIM and would like to use it.
After going to the documentation I would like to know how do I can use APIM for my specific enpoint and where I allow users to generate API's in my client side react app.
I am also going through the API management API. but don't know how to generate user specific API keys...
You could simply mimic what the Developer Portal does using APIMs REST API.
If you are using the Consumption Tier of APIM, you can just create a standalone subscription using the Create or Update Subscription API. Yon don't have to set properties.ownerId in the request payload here.
On the other tiers, standalone subscriptions are not supported yet (but will be as mentioned in the official announcement blog under New Features), so you will have to create a user first using the Create or Update User API and then create a new subscription mentioning this user under properties.ownerId as /users/{userId}.
Since these REST APIs call the Azure Management API, you shouldn't be making these requests from the client and instead should be calling this from your backend.
In our organization we have an in-house developed web based application that make use of Google Data (GData) APIs(gdata-java-client) API to manage email user accounts, email settings, nickname, profile updates , contact management. This application was built some years back. Recently we planned to enhance some features and had a look at the API and Google API website. Looks like some of the GData APIs are getting deprecated or planning to take down(April 20, 2015). We are using below GData APIs and want to confirm/check which all APIs we need to migrate immediately to new Google APIs Client Library for Java (google-api-java-client) so that the services can function smoothly.
1) Google Apps Provisioning API - V2 (URL used - https://apps-apis.google.com/a/feeds/{ourdomain}/user/2.0)
For Creating User/Update User/Delete User/Nick Name
2) Google Apps Email Settings API - V2 (URL used -https://apps-apis.google.com/a/feeds/emailsettings/2.0/{ourdomain}/{username}/webclip)
For Disabling WebClip
3) Google Apps Profiles Data API - (URL Used - {hostname}/m8/feeds/profiles/domain/{ourdomain}/full/{username})
For Retriving and Updating Profile
4) Google Domain Shared Contacts API - (URL Used - {hostname}/m8/feeds/contacts/{ourdomain}/full)
For CreateContact/DeleteContact / UpdateContact
Jars/Versions of GData Libs that we are using today.
gdata-client-1.0.jar : 1.46.0 / gdata-core-1.0.jar : 1.46.0 / gdata-appsforyourdomain-1.0.jar : 1.3.1 /gdata-contacts-3.0.jar : 3.1.0
Please let us know what all APIs will be taken out of service on April 20,2015 and also please provide the new APIs that we can use for coding the migration. Do we also have any migration guide ? Can we keep gdata-java-client jars and google-api-java-client jars together in the class-path. We would like to migrate the services which are going to brought down by April 20, 2015.
We had completed the migration and thought will update the thread and it might help someone else. Below APIs/components are getting shutdown by April 20, 2015.
1) Google Apps Provisioning API Migrated to ADMIN Directory API
2) Google Apps Profiles Data API --> Migrated to --> ADMIN Directory API
3) ClientLogin --> Migrated to --> OAuth 2.0
Google Apps Email Settings API is still under GDATA API but its placed under ADMIN SDK. No need to migrate this. But we were using ClientLogin Auth model so we need to move to OAuth 2.0
Also for using ADMIN SDK you need to make changes in Google Developer console and Admin console. Details in below links.
https://developers.google.com/admin-sdk/directory/v1/guides/prerequisites
https://developers.google.com/admin-sdk/directory/v1/guides/delegation
I'm using Exchange web services, trying to create a calendar entry in another user's mailbox. My account in EWS has rights to do this, and I can successfully use Impersonation to create thes appointment in any mailbox.
However, some examples I've seen of doing this, use an instance of DistinguishedFolderIdType, not impersonation, to set the mailbox for the appointment.
Problem is, this class simply isn't appearing in my installation of the EWS SDK for Visual Studio. It's v1.1, obtained here, but can't be found in Object Explorer. What am I missing?
The type DistinguishedFolderIdType is not part of the EWS Managed API.
If you do not use the EWS Managed API but generate your own SOAP client proxy manually from Visual Studio by adding a reference to the EWS .asmx service, the generated proxy will contain DistinguishedFolderIdType.
However, depending on what you are trying to accomplish, you should be able to do it using the classes provided på EWS Managed API 1.1 and you won't need DistinguishedFolderIdType.