Hot answers tagged

8

Windows Azure is PaaS(Platform-as-a-Service) that allows you to install and manage your SharePoint environment on cloud like you do on premises. You will be charged based on the space and compute hours consumed by your SharePoint farm, Visual studio, TFS etc. Much VS debugging makes you pay more :-), hence development farm on Azure may be costly to ...


4

It might be worth a shot to try adding ACS as an App in Azure AD, configure it for Single Sign-On and then using the WS-Federation end point for the app to add the Identity Provider. The first part of this post has a more detailed walkthrough: http://blog.helloitsliam.com/Lists/Posts/Post.aspx?List=e10cb685-6b5c-4b6c-aaf4-e1d122d57174&ID=120


4

You can get an idea about where your Office 365 data is stored at Microsoft Online Services - Where is my data? According to that your data is probably in the region closest to where the admin stated the company resided. If you're using CSOM (Client Side Object Model) from server code then you should probably place your App in the same region. But if your ...


4

ConvertTo-SPOMigrationTargetedPackage - Re-maps a previously created file share based package or exported SharePoint package to accurately describe objects in a target web. New-SPOMigrationPackage - Creates a new migration package based on source files in a local or network shared folder. Set-SPOMigrationPackageAzureSource - Creates Azure containers, upload ...


3

It's not enough to mark the SharePointContext, SharePointAcsContext and SharePointContextToken serializable. You must implement ISeralizable interface. In there are three method declaration. One constructor for the deserialization, and two for the serialization. The following link refers to a msdn article, that's about how to implement it correctly. In ...


3

An on-premises equivalent to timer jobs is a console application that is run via the OS's scheduler service. (An "at" job for all of us old-timers.


3

The best region would be whatever is closest to you. As far as I know, these are the general locations of the Azure data centers: North Central US – Chicago South Central US – San Antonio West US – California East US – Virginia So if you are rolling a provider hosted app in Azure, you'd want to tie your Azure servers to the region that is closest to you.


3

You can use this REST endpoint: https://<server>/_api/sp.userprofiles.peoplemanager/getPropertiesFor(@v)?@v='domain\LoginName' This retrieves all profile information for the given LoginName. You can select the property PersonalUrl by adding $select = PersonalUrl For more information see the User profiles REST API reference at MSDN.


2

I have just had the same issue in my environment. In my case I have HTTP enabled on the workflow farm. During re-install the workflow farms HTTP endpoint disappeared (you can run the Get-WFFarm PowerShell command and check the Endpoints there). So the solution in my case was to properly configure the HTTPS endpoint and than re-register the workflow farm ...


2

If you're developing Provider hosted apps for on-premises SharePoint you have two options: High Trust Low Trust High Trust The trust between SharePoint and the App is based on a certificate which the App uses to sign the token in it's request to SharePoint, this certificate is then added to the SharePoint farm and SharePoint will trust that the User ...


2

For me: Recycle time (time from recycle or IISRESET until we actually get a SharePoint page). That is the biggest culprit with developing for SP 2013 for me personally. Also, the perceived experience with debugging a solution (since it tends to time-out...) would be nice. No idea how to quantify that to a metric though.


2

You can limit to the SharePoint online services IP address ranges: https://support.office.com/en-US/Article/SharePoint-Online-URLs-and-IP-Addresses-99b11563-c42d-4c20-87d2-502e66d62164?ui=en-US&rs=en-US&ad=US All Office 365 services address ranges are documented here: http://technet.microsoft.com/en-us/library/hh373144.aspx


2

Is it possible to use existing on premise AD with Azure/AWS hosted SharePoint 2013?: You can extend their on premise AD with Active Directory Federation Services (ADFS). Since SharePoint 2013 supports claims based authentication, they can then leverage ADFS as an identity provider for their SharePoint 20103 Virtual Machines. is it possible to make the load ...


2

When you delete a user account, the account becomes inactive. However, for approximately 30 days after you have deleted it, you can restore the account and the associated data. If your organization synchronizes user accounts to Office 365 from a local Active Directory environment, you must delete and restore those user accounts in your local Active ...


2

"People" will show only those users who have been assigned "Exchange Online" license. It is possible to add Users to your Office 365 without giving them any of the Office 365 subscription, except "Mobile Device Management for Office 365" which is mandatory. And any user you add through Office 365 also gets added into Azure AD.


2

An Azure AD instance is already setup in the background for each Office 365 tenant. Essentially what's meant with Signing Up is getting an Azure account so that you can access to further settings of Azure AD (such as customizing you Office 365 login page).


2

You need to allow CORS to be able to do this. The problem is that javascript doesn't allow cross domain calls, and the Azure service can't have the same domain name as your Office 365 (At least I'm pretty sure of this). By enabling CORS support in your Azure REST API, you can circumvent this. Do be warned however, that CORS must be supported by the browser ...


1

A simple solution would be upon the first request to your long running task to write a stutus started to a persistent storage e.g. azure table storage. The key could then be username_webid. Upen subsequent request you can check if the long running task is started and maybe provide a progress if your task updates the table row. Im surprised if the ...


1

SharePoint client object model (v15) won't work in Azure because it requires Client components and in Azure they aren't installed. Please check the link to see the detail explanation As workaround you can try rewrite to last version (v16) it supports portable versions of libraries. Also you can create own virtual machine and manually install client ...


1

For Office 365 Enterprise and MidSize Business you can set a users Password to never expire using Connect to Windows PowerShell by using your company admin credentials. Run the following cmdlet: Connect-MsolService Do one of the following: To set the password of one user to never expire, run the following cmdlet by using the UPN or the user ID of the ...


1

You can remember that BeforeProperties and AfterProperties are different for Sync. and Async. events BeforeProperties and AfterProperties behavior is different for List Items and Library Items If you investigate and test BeforeProperties and AfterProperties behavior in these cases - be ready that it could be all broken if you use Publishing template site ...


1

It turned out that the solution was very simple, the Sharepoint Client Dlls, were not set to Copy Local True, it was false. Changing this flag fixed my problem. ...


1

1) Didn't work with Visual Studio Online, but I don't see any differencies between Your 'real' dev machines and Azure. You can use what You want like on a standalone machine too 2) I use TFS online http://tfs.visualstudio.com in azure vms. Will be free if team is up to 5 3) All like in real life, You can put Your machines in one network and share SQL ...


1

I've created a PowerShell script to add all the 59 IP ranges mentioned in the SharePoint Online URLs and IP Addresses document as Jim pointed out. Connect to your Azure subscription using PowerShell, replace the $AzureSqlServerName variable so it contains the name of your SQL Azure database instance and run the following PowerShell script: ...


1

Although I still don't know the exact cause of the error above. I did manage to get to work. I uninstalled the app from all the site collections and from the SharePoint store. Generated a new clientid and secretkey, increased the version number of the app, updated the clientid in the publish wizard and reinstalled the app on the SharePoint server. (The ...


1

If your looking at the portal capability, provisioning capability etc , check out Azure Pack http://www.microsoft.com/en-us/server-cloud/products/windows-azure-pack/ . This is to incorporate onto your On-Premises DC. Cheers


1

Office 365 (formerly known as SharePoint online) is a cloud counterpart of SharePoint on-premises. There two types of apps which are cloud based: AutoHosted apps and Provider hosted apps. The main difference is that with auto-hosted apps all Windows Azure and Windows Azure SQL Database components are provisioned for you when the app is installed and ...


1

The scenarios you could use with SharePoint are: Save the database file in SharePoint itself and check it in and out when you're using it just like you'd do with any other file. This is kind of rickety and SP isn't really going to do a great job of telling you what changes you made, but it's possible, I guess. Use Access Services to, in essence, host the ...


1

As long as you have the legal license.


1

I don't see why not. I havn't tried myself, but as long as you put your VMs and storage accounts in same affinity group, I would assume that Azure's internal disks are fast enough to be wihtin the 20ms latency requirement, but a test would be the only way to know for sure. Also be sure to look into striping your disks if you want to obtain good IOPS. Read ...



Only top voted, non community-wiki answers of a minimum length are eligible