Can't associate Office 365 with Azure subscription - azure

For my company, I have an Office 365 E3 subscription (not trial).
My office 365 account is also global admin.
Now I would like to use Office 365 API. According to the getting started tutorial I was told to associate Azure with Office 365.
So I when go to Office 365 Admin panel then click to Azure AD. I end up with Azure Sign up screen however the screen is empty. What am I missing?

It may not be a development question, but as there is no O365 forum, an answer can still be provided, which this site is all about.
You need to go on this website https://manage.windowsazure.com/ and register to access your Azure AD. It takes few minutes to proceed.

there's a new getting-started flow that might make this easier in the future, in case others hit this as well on http://dev.office.com/getting-started/office365apis.

The problem appears to be my browser is blocking third party cookies . When I turned that option, it worked.

Related

PowerBI - Service Principal access

Trying to publish report in PowerBI using Service account. These are steps I did. I'm starting to learn this, so please correct me if I did anything wrong.
Created Microsoft 365 account, as Power BI wont take personal email to sign up.
Signed up for Power BI, activated pro account.
Need to invoke REST method, so I signed in using same Microsoft 365 account to Azure. With this account, when I try to add subscription, its taking me to page to select offers for subscription.
I have another Azure subscription, but I'm not able to change directory of Azure account I created with Microsoft 365, as I need subscription to do that.
So I thought fine, will do a subscription for Microsoft 365, but it has payment information with country defaulting to United States. It wont take my credit card info.
Is this wrong way of doing this automation? How to change directory without subscription, or should I dont even have to do this part?
Thanks in advance for any suggestions.
If you want to solve the payment info defaulting to USA, you can change your geo location. Use this list to find your Geographical location identifier (Hex)
then use this command to change it
Set-WinHomeLocation -GeoId $hex
Now try inputting your CC info, and it should show your country instead of USA.

Is there any Node js or REST API to create new users in office 365.

I have purchased office 365 essentials plan. I have got an admin account. Office provides user interface to add new users under this main admin account.
What I need is I want a Node js or REST API to create users on this account. I have googled well, can't met anything like this. Anyone can provide any samples on this. Any help would be appreciable.
Office 365 Users are hosted in the background by Azure Active Directory. I believe you should be able to create new accounts for your Office 365 programmatically using the Azure Active Directory Graph API, or probably even better, using the Microsoft Graph API.
Check out the documentation here:
https://graph.microsoft.io/en-us/docs/api-reference/v1.0/api/user_post_users
You should be able to get a jump-start using our public samples located here:
https://graph.microsoft.io/en-us/code-samples-and-sdks
I hope this helps!

Google apps sso into office 365

I am trying to let my google apps users login into office365 using google apps credentials but I am unable to find setup page on microsoft azure ad or office 365 account I followed https://support.google.com/a/answer/6363817?hl=en instructions but could not find instructions on Office 365 side. Does any one know where to find the setting page.
I've been battling this for a couple of days now.
The key is: you must use PowerShell to do the AzureAD settings:
Install AzureAD plugin for Powershell as described in the lower part of the page here: https://technet.microsoft.com/library/jj151815.aspx
Then this guys instructions helped me greatly:
http://www.viewds.com/blog/making-office-365-work-with-an-external-saml-identity-provider.html
I'm at a point where I get redirected from office.com to Google's login page as soon as I type my email address with our company domain. but then the login fails (but it worked 1 single time oddly enough). Let me know if you get any further!
Cheers
:Phil

Using Office 365 API with only one account

I am trying to use the Office 365 API to write events to the calendars of anyone at our organization. This should not involve the users logging in to Office 365 at any point. The events to add are written out at various points during the day (when the user who would own the event may not even be at a computer), so the per-user token approach doesn't even make sense.
It appears that Microsoft provides an alternative that uses a service account. This account can be used to write to any user's calendar (or sending email as any user, etc.). However, I can't find any documentation on doing this. Could anyone provide a link to it?
I found a blog post on this topic: http://blogs.msdn.com/b/exchangedev/archive/2015/01/21/building-demon-or-service-apps-with-office-365-mail-calendar-and-contacts-apis-oauth2-client-credential-flow.aspx
Also, if you aren't using Microsoft's client library for this (for example, if you use linux), you'll need to see this too: Office 365 Rest API - Daemon week authentication

Software development start-up: Signing into Microsoft services

We are a start-up software company with around 15 developers. We are almost entirely using Microsoft's technology stack.
A problem that we have at this point is the confusion between signing into Microsoft's online services.
Each developer has two accounts: an Office 365 account and a Windows Live account. The Live account is created from the Office 365 account's email address. So, essentially, we have one email address but two accounts (and thus two passwords).
When logging into an online service, we are often greeted with the following:
For many, this becomes a hit and miss with their various passwords until access is granted. From what I understand:
Work or school account: An Office 365 account OR an account set up in Active Directory?
Microsoft account: A Windows Live account?
Next, can Azure Active Directory help us in any way here?
Are we able to somehow unify our accounts so to have a "single sign-in" for Microsoft's online services?
EDIT:
Further comments on Dushyant Gill answer below.
If we don't need to register our Office365 accounts as Live accounts, then how would I typically add a user to the Azure Active Directory?
When creating a new user, I only have three options:
I guess the last option would be the correct approach if we wanted to move away from Live accounts. I want to add a user to my Azure AD from my Office365 AD?
When I try to do this, I get the following error:
Do I have to link the directories somehow?
davenewza, yes you can take action to improve the experience here (it won't be simple - but given the number of users in you company - it shouldn't be that difficult)
First, your company already has an Azure Active Directory - it is the directory behind your Office 365 subscription. Azure AD authenticates your company's users when they sign in to Office 365 services.
Second, you should use your Azure AD accounts (work or school account) to signup and access other Microsoft services that are meant for businesses: Microsoft Azure, Visual Studio Online, Microsoft Dynamics etc. The disambiguation screen that you see (pasted in your question) only shows up when you're signing in to a service that supports both Azure AD as well as Live accounts. So, move your Azure and other business services subscriptions to use Azure AD accounts and as a thumb rule - your companies users will always select the 'work or school account' option (if ever they see that screen).
Finally, let's get rid of that screen altogether: do you really need the live accounts to run your business? (what Microsoft services are you using that need live accounts?) If none, great - once you've moved your subscriptions to Azure AD accounts - get rid of the live accounts. If you indeed need them - change their emails (add an _live suffix to them) - you as it is have two password - different user names will reduce confusion.
Note that the second step will require you to call Microsoft support (or file online tickets) to move subscriptions for some services - however the risk of downtime is low because you already have Azure AD accounts - you might need to reconfigure permissions once the subscriptions are migrated.
I am with the Azure AD team - get in touch with me if you're stuck - contact me on http://www.dushyantgill.com
Best of luck.
ps: we are working to improve this experience - such that folks like you don't end up in this position in the first place. Stay tuned.

Resources